Messages between microservices come in three different flavors: Commands, Queries, and Events. Commands change the state, queries request the state, and events share the state. When designing microservice communication patterns, it is important to understand the role of these messages. Following a clear set of rules can help ensure consistency and clarity within your system of microservices.

Learn the basics of Apache Flink® and how to get started with simple, serverless Flink! Flink is a powerful, battle-hardened stream processor that has rapidly grown in popularity, becoming the de facto standard for stream processing and a top-five Apache project. Kai Waehner, Field CTO at Confluent, explains how Flink fits into your data streaming architecture, why stream processing is needed for real-time data, and how Flink’s underlying architecture provides a number of advantages.

Confluent is pioneering a fundamentally new category of data infrastructure focused on data in motion. Confluent’s cloud-native offering is the foundational platform for data in motion – designed to be the intelligent connective tissue enabling real-time data, from multiple sources, to constantly stream across the organization. With Confluent, organizations can meet the new business imperative of delivering rich, digital front-end customer experiences and transitioning to sophisticated, real-time, software-driven backend operations.

Asynchronous events are a communication pattern that is used to build robust and scalable systems. These events are often pushed through a messaging platform such as Apache Kafka. Among their benefits are the ability to optimize resource usage, more flexibility for scaling, and new ways to recover from failure without losing data.

Streaming data brings with it some changes in how to perform joins. In this video, David Anderson and Dan Weston talk about how and when to use temporal joins to combine your data.

Continuous Integration (CI) is the process of automatically building and testing your code on every source control commit. Continuous Delivery (CD) takes this further and automatically deploys the code to production on every commit. Used together these techniques allow code to be built, tested, and deployed automatically through a robust CI/CD pipeline. CHAPTERS.

Lucia Cerchie explains what an Apache Kafka® Consumer Group ID is, and what role it plays in work sharing and rebalancing.

Polyglot Architecture is a feature of microservices that allows each microservice to be built using a different technology stack. This approach provides developers the freedom to select the best tools for the job and allows them to be more creative with their solutions. However, like with any powerful tool, it can have negative consequences if it isn't used properly. CHAPTERS.

From vehicle communication to predictive maintenance, real-time ingestion, analysis, and control has become an increasingly important characteristic of the machines we use in everyday life.

The Branch by Abstraction Pattern is a method of trunk-based development. Rather than modifying the code in a separate branch, and merging the results when finished, the idea is to make modifications in the main branch. An abstraction layer is used to ""branch"" the code along an old and new path. This approach has some key advantages, especially when decomposing a monolith.