Task application topologies in addition to a single Batch or Task application • Each box is a Spring Batch or Task application. • Application Flow can split and join, based on optional conditional expressions
Once in the DB the batch process can consume Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum
are broken into individual events File and web service events are processed by streaming applications All streaming apps are custom. (Didn’t use any off the shelf applications) Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum
apps are designed to be idempotent Load can be spread out much better Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Error handler
are broken into individual events Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Lorem ipsum Spring Batch
Devs love this) • Changes can be tested locally • Custom templates • Dependency management (Solution BOM) • Easy to understand applications that are small and do one thing • Unit and integration testing is easy • Containers Paving the road to production
Helm Charts) • Message broker is Apache Kafka • Customized to use non-OSS database • JDK17 Stream and Batch applications • GitOps ◦ Applications are defined in git ◦ Stream definition (DSL) and deployment info is in git ◦ Deployments via Dataflow REST API
• Monitor topic lag • Logs exported via sidecar application Scaling • Make sure JVM properties are set (Heap memory, CPU count, GC, etc) • Single instance of most apps • No dynamic scaling yet