Kubernetes

Heavyweight Stream Processing Frameworks are another foundation/pattern to build your microservices.

These frameworks are highly scalable and allow you to efficiently solve many analytical tasks. But they are not always good for stateful event-driven microservice application patterns.

Heavyweight frameworks operate using centralized resource clusters, which may require additional operational overhead, monitoring, and coordination to integrate successfully into a microservice framework. However, recent innovations move these frameworks toward container management solutions (CMS) such as Kubernetes that should reduce your efforts.

Introduction into Event-driven microservice (EDM) architecture consists of the following topics:

• two topologies
• content of events
• three types of events
• table-stream duality
• schemas for defining event data
• single writer principle
• features of event broker
• event broker vs message broker
• single source of truth principle
• scaling using containers and VMs
• microservice taxes that we should pay

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

🚆✈️🚌🛳 + Math + Highload + Machine Learning…

Two and a half years ago we’ve got a request from the Travel-business IT company, whose B2C IT solution is the basis for one of the world’s largest travel companies that serves over 1 billion passengers every year.

What did they want to achieve?

They wanted to quickly design and implement an “internal startup” - an innovative B2B/B2C solution for the travel industry.