Round Robin

How to integrate event-driven microservices with request-response APIs?

There are two types of external events:

• Autonomously Generated Events (analytical events)
• Reactively Generated Events (events from request-reply)

There are two approaches of processing and serving requests using stateful services:

• using internal state stores (with silly or with smart routing)
• using external state stores (with regular or with composite microservice)

Ways of handling requests within an event-driven workflow:

• Handling requests directly
• Turning requests into events (big latency)
• Processing events for user interfaces (a mix of two ways)

Approaches for request-response applications, their pros and cons:

Earlier the book club of our company has studied excellent book:

Martin Kleppmann - Designing Data-Intensive Applications

This is the best book I have read about building complex scalable software systems. 💪

As usually I prepared an overview and mind-map.

Chapter 6 contains everything the DEV team should consider when designing storage for big data:

• Partition aka Shard aka Region aka Tablet aka vNode aka vBucket. It is another approach for storing the data in addition to Replication (reviewed in the previous chapter)
• How to partition key-value data (primary index). Problems with partitioning - skew and hotspot. Approaches: key range and hash of key.
• Partitioning for secondary indexes: Local index and Global index
• Rebalancing partitions as you grow. Bad and good aproaches, problems and how to deal with them. Manual vs automated rebalancing.
• Request routing. Different aproaches, issues and solutions.

Download full mind map (PDF)