One of the goals of building microservice-based architectures is to reduce the complexity of individual components. In doing so, some of that complexity shifts from individual services towards interservice communication. You may have bumped into the terms orchestration and choreography in your research on the topic. While the web offers a vast range of articles that carefully outline the pros and cons of each pattern, the real challenge is left to the reader: deciphering which pattern best fits your specific use case by understanding which arguments apply to your use case and weighing only the relevant ones in your decision.

Are you a Developer curious about Apache Kafka? Have you never had the time to dig into it?

No problem. In this session, we will dig into it. We will go on a journey to unveil how I’ve built an event-driven system to power my Patreon account using Kafka. We will focus on the parts you need to know to build Event-Driven Applications. Explore the basic concepts and recommendations. And learn about how to use C# and KafkaFlow, an Open Source framework for .NET.

With an increasing need for scalability and performance dictated by the modern web, it becomes harder and harder to choose an API paradigm that is suitable for service-to-service communication.

While the classical models still work and have their own merits, some of them rely heavily on documentation, extensive coordination between teams or code-sharing. We use shared libraries, and over time our projects become intertwined with dependencies. In these cases, we need something to untangle those and reduce coupling. Welcome gRPC.