InfoQ Homepage Event Driven Architecture Content on InfoQ
-
/articles/shadow-table-strategy-data-migration/en/smallimage/Shadow-Table-Strategy-for-Seamless-Service-Extractions-and-Data Migrations-thumbnail-1744019310168.jpg)
Shadow Table Strategy for Seamless Service Extractions and Data Migrations
The shadow table strategy creates a synchronized duplicate of the data that keeps the production system fully operational during changes, enabling zero-downtime migrations. The approach supports diverse scenarios - including database migrations, microservices extractions, and incremental schema refactoring - that update live systems safely and progressively.
-
/articles/choosing-message-broker/en/smallimage/beyond-trends-thumbnail-1741943360849.jpg)
Beyond Trends: A Practical Guide to Choosing the Right Message Broker
Choosing the right message broker for your application requires matching the appropriate technology with the messaging patterns needed. Message brokers can be broadly categorized as either stream-based or queue-based, each offering unique strengths and trade-offs.
-
/articles/rig-data-consistent-microservices/en/smallimage/GettyImages-637899158-small-1716883672077.jpg)
Introducing the RIG Model - the Puzzle of Designing Guaranteed Data-Consistent Microservice Systems
The RIG model formulates three rules for a saga call chain. Using a gamified RIG tool, consisting of three main RIG puzzle pieces, teams can model a microservice system that guarantees eventual data consistency.
-
/articles/kafkaflow-dotnet-framework/en/smallimage/building-kafka-event-driven-applications-with-KafkaFlow-small-1693903734363.jpg)
Building Kafka Event-Driven Applications with KafkaFlow
KafkaFlow, a .NET open-source project, simplifies Kafka-based event-driven app development with features like middleware for message processing, enhancing maintainability, customization potential, and allowing developers to prioritize business logic.
-
/articles/event-driven-architecture-clouds/en/smallimage/a-comprehensive-guide-to-building-event-driven-architecture-small-1687167469391.jpg)
A Comprehensive Guide to Building Event-Driven Architecture on Azure, AWS, and Google Cloud
In this article, you'll find guidance to Azure, AWS, and Google Cloud resources, along with unique architecture examples that incorporate the AWS EventBridge, SNS, Azure Service Bus, Eventgrid, and Google Cloud Eventarc. These examples can help you better grasp the resources’ concepts and enable you to kickstart building your own architecture using an event-driven approach.
-
/articles/eda-mediator/en/smallimage/event-driven-architecture-with-mediator-topology-small-1685547200315.jpg)
A Case for Event-Driven Architecture with Mediator Topology
This article tells the story about a business case using Event-Driven Architecture with Mediator topology and an implementation that provided elastic scalability, reliability, and durable workflows. All were built using Kubernetes, KEDA, AWS, and .NET technologies.
-
/articles/kafka-clusters-cloudflare/en/smallimage/tales-of-Kafka-at-Cloudflare-small-1684768928637.jpg)
Tales of Kafka at Cloudflare: Lessons Learnt on the Way to 1 Trillion Messages
Cloudflare uses Kafka clusters to decouple microservices and communicate the creation, change or deletion of various resources via protobuf, a common data format in a fault-tolerant manner. The authors suggest investing in metrics for problem detection, prioritizing clear SDK documentation, and balancing flexibility and simplicity for standardized pipelines.
-
/articles/billions-messages-minute/en/smallimage/LOGO-1679471830613.jpg)
Billions of Messages Per Minute Over TCP/IP
Chronicle Wire offers an alternative way of transferring data between systems, delivering more messages, faster, than common JSON/XML approaches. This approach to data serialization improves both latency and throughput.
-
/articles/microservices-async-migration/en/smallimage/logo-1662728174698.jpg)
Migrating Netflix's Viewing History from Synchronous Request-Response to Async Events
In a web-based service, a slowdown in request processing can eventually make your service unavailable. Chances are, not all requests need to be processed right away. Some of them just need an acknowledgement of receipt. Have you ever asked yourself: “Would I benefit from asynchronous processing of requests? If so, how would I make such a change in a live, large-scale mission critical system?”
-
/articles/streaming-first-real-time-ml/en/smallimage/streaming-ml-small-logo-1660833205193.jpeg)
Streaming-First Infrastructure for Real-Time Machine Learning
This article covers the benefits of streaming-first infrastructure for two scenarios of real-time ML: online prediction, where a model can receive a request and make predictions as soon as the request arrives, and continual learning, when machine learning models are capable of continually adapting to change in data distributions in production.
-
/articles/network-proxy-stream-processor-pipy/en/smallimage/logo-1643366806668.jpg)
How to Create a Network Proxy Using Stream Processor Pipy
In this article we are going to introduce Pipy, an open-source cloud-native network stream processor. After describing its modular design, we will see how to rapidly build a high-performance network proxy to serve our specific needs. Pipy has been battle-tested and is already in use by multiple commercial clients.
-
/articles/microservices-inside-out/en/smallimage/turning-microservices-inside-out-small-image-1627634447180.jpg)
Turning Microservices Inside-Out
Turning microservices inside-out means moving past a single, request/response API to designing microservices with an inbound API for queries and commands, an outbound APIs to emit events, and a meta API to describe them both. A database can be supplemented with Apache Kafka via a connecting tissue such as Debezium.