Recovering

The 4th pattern to build microservices is to use Lightweight Frameworks.

Lightweight Frameworks provide similar functionality to Heavyweight Frameworks, but they heavily rely on:

• the event broker
• the container management system (CMS)

In many cases they exceed Heavyweight Frameworks.

Different apps can use any/different resources from the cluster which are better fit their needs. While still provide Scaling and Recovering from Failures (again by heavily relying on event broker and CMS).

Overviewing basics of event processing in Event-Driven Architectures:

• Typical structure of microservice
• Typical types of event transformations, 2 branching scenarios, merging streams
• Repartitioning events and when it can be useful
• Copartitioning events and when it is needed
• Assigning Partitions to a Consumer Instance. Three strategies to do this.
• Recovering from stateless processing instance failures.

These topics are disclosed in the Chapter 5 of the book we are currently studying:

“Building Event-Driven Microservices: Leveraging Organizational Data at Scale” by Adam Bellemare