Apache Ignite Extensions - Modularization
summary
Apache Ignite moves over ten streaming and connector modules (Flink, Kafka, Flume, MQTT, ZeroMQ, RocketMQ, Storm, Twitter, Camel, JMS and new community Pub-Sub and Spring Boot autoconfigure modules) into a separate repository so each has separate release lifecycles. Build and CI stay on TeamCity and Travis; release process adds a compatibility matrix and independent versioning. Demo shows DataStreamer and a Kafka streamer with autoflush=1s and allowOverride=true consuming a local topic and successfully writing ~100 events into an Ignite cache.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:23Apache Ignite structure
- 7:03Release cycle problems
- 9:56Modularization solution
- 15:27New system benefits
- 17:33Ignite streaming
- 19:41Streaming API demo
- 27:01Kafka extension demo
- 35:24Summary and future plans
- 36:06Q&A
related talks
46mFrom Chaos to Cohesion: Building Modular Monoliths in the Real World
48mSpring Modulith: What the What?
36mMicroStream Labs – New Incredible Feature Preview
45mThe State of Flink and how to adopt Stream Processing
01h 11mSpring Modulith – Spring for the Architecturally Curious Developer
45mCode Once, Use Everywhere: Building a Shared Module used by Multiple Projects
27mBatch/Stream Ask-Me-Anything
31mSharing is caring: Building a modern microservice architecture helps everyone get ahead