InfoQ Homepage Event Driven Architecture Content on InfoQ
-
Event Sourcing in an Unreliable World
Examples of event sourced systems are often from process-oriented domains, like e-commerce, with incoming commands that generate events. But there are domains without processes that are intrinsically unreliable where we are collecting events from external event sources with transports that are unreliable, Lorenzo Nicora explained at the recent Microservices Conference µCon London 2017.
-
Jonas Bonér on How Events Are Reshaping Modern Systems
Jonas Bonér talked about event driven services and how event driven architectures (EDA) and event stream processing (ESP) technologies are helping with designing the modern applications based on distributed systems. He spoke at the recent Reactive Summit 2017 Conference.
-
Designing Event Sourced Microservices
Event sourced microservices is an area that hasn’t been explored nearly as much as it should be, Greg Young claimed at the recent Microservices Conference µCon London 2017, but he also strongly emphasized that you should not event source all your microservices. Instead, he recommends looking at individual services and applying the event sourcing pattern to services that actually benefit from it.
-
Vaughn Vernon Uses Reactive DDD to Model Uncertainty in Microservices
Microservices and reactive systems bring with them uncertainty about messages arriving out of order, multiple times, or not at all. How to react to such uncertainty is a business decision, says Vaughn Vernon, and is best captured by modeling the uncertainty using concepts of Domain-Driven Design.
-
Event Architectures and Event Streaming
When moving from a monolithic system to a distributed or microservices system, you commonly also move from a single source of truth in one database to many databases and thus many sources of truth. Using an event architecture and persisting all events as a stream can give back the single source of truth, Ben Stopford claims in one of a series of blog posts about events, event streams and Kafka.
-
Selecting an Event Architecture
When designing a distributed system, maybe based on microservices, and you are considering an event architecture, there are several models and technologies available. When choosing how to implement the architecture the non-functional requirements are a main factor, David Dawson claims when describing different styles of event architectures in a recent blog post.
-
Microsoft Ships Azure Event Grid for Unified Event Processing
Today, Microsoft released a novel service for ingesting and processing cloud events. The Azure Event Grid takes events generated from Azure services, or custom apps, and routes them to chosen handlers.
-
Amazon CloudWatch Events Gains Cross-Account Event Delivery
Amazon Web Services (AWS) recently added cross-account event delivery to Amazon CloudWatch Events to support use cases such as the tracking of events across an entire organization and the handling of events in separate accounts to implement advanced security schemes.
-
Process Managers in Event-Based Systems
Publishing events to notify about changes in a domain keeps different domains decoupled from each other, but if there really is a logical flow of events it becomes implicit and hard to follow. A better solution is to use a Process Manager to keep track of the overall process, Bernd Rücker stated in his presentation at this year’s DDD eXchange conference.
-
Versioning of Events in Event Sourced Systems
A challenge with event sourced systems is that events put in the event store years ago must be readable today, even though the software has gone through numerous changes, Greg Young stated in his presentation at this year’s DDD eXchange conference. If a system can be taken down, versioning of events is relatively simple. The real challenge comes when a system can’t be taken down.
-
Managing Data in Microservices
Randy Shoup from Stitch Fix team spoke at QCon New York 2017 Conference about managing the data and isolated persistence in Microservices based applications. He also talked about events as a first class construct for microservices.
-
Overview of the Reliable Event Delivery System at Spotify
Spotify clients generate up to 1.5 million events per second at peak hours and all are handled by their Event Delivery System, designed to have a predictable latency and to never lose an event, Igor Maravic noted in his presentation at the recent QCon London conference, where he gave a high level overview of the system and some of the key operational aspects.
-
Concurrent and Distributed Programming in the Future
The world is concurrent with everything around us asynchronous and event oriented. Concurrency and the cloud are things every developer will have to deal with in the future, Joe Duffy claimed in his keynote at the recent QCon London conference. At the heart of this is communication, which is essential both for concurrent and distributed systems.
-
Hazelcast Release Jet, Open-Source Stream Processing Engine
Hazelcast, previously known for the open-source caching and in-memory data grid technologies, has announced a major release of their new stream processing engine, Jet.
-
Moving a Monolithic Application towards a Microservices Architecture
Migrating an existing system towards microservices is very different from building a new micoservices-based system, Joris Kuipers, architect at Trfork Amsterdam, claims in a presentation describing an ongoing process of refactoring a large monolithic application, based on CQRS using Axon framework, towards a microservices architecture.