InfoQ Homepage Event Driven Architecture Content on InfoQ
-
Patterns in Distributed Systems
In a series of blog posts, Mathias Verraes describes patterns in distributed systems that he has encountered in his work and has found helpful. He currently describes 16 patterns in three areas: patterns for decoupling, general messaging patterns and event sourcing patterns. His goal is to identify, name and document the patterns together with the context in which they can be useful.
-
Experience Building Distributed Systems and Microservices — Jeppe Cramon at Micro CPH
We must understand the business domain we are working in, identify the bounded contexts and the business capabilities, and design our services using this knowledge. In a presentation at Micro CPH, Jeppe Cramon talked about his experience working with distributed systems, microservices and the principles and patterns he sees as beneficial for successfully creating microservices based systems.
-
Microsoft Evolves Azure Event Grid: New Telemetry Events, Advanced Filters, and Event Domains
In a recent blog post, Microsoft announced several new updates to its cloud service Azure Event Grid, ranging from new telemetry events from IoT Hub to the general availability of advanced filters and Event Domains.
-
Amazon Managed Kafka Aims to Simplify Kafka Streaming Setup and Use
Introduced as a public preview at AWS re:invent 2018, Amazon Managed Streaming for Kafka (MSK) is now generally available. Amazon MSK aims to make it easy to build and run streaming applications based on Kafka.
-
Experiences Going from Event-Driven to Event Sourcing: Fangel and Ingerslev at MicroCPH
At MicroCPH 2019, Thomas Bøgh Fangel and Emil Krog Ingerslev, both at Lunar Way, a fintech company, described how after building a monolithic Rails application they decided to migrate to an event-driven microservices architecture. During the migration they found some design issues and decided to move to event sourcing. In their presentation they discuss the problems and how they solved them.
-
Microservices Framework Lagom 1.5 with Akka Management and Support for Kubernetes and OpenShift
Version 1.5 of the microservices framework Lagom comes with Akka Management, a set of tools for operating Akka powered applications, and support for deployment with Kubernetes or OpenShift. The recently released version 1.5 is built on Play 2.7.0, Alpakka Kafka 1.0 and Akka 2.5.22 and also adds support for Couchbase and for gRPC through Akka gRPC.
-
Event Streams and Workflow Engines – Kafka and Zeebe
In a recent joint meeting in Amsterdam, Kai Waehner described features of Apache Kafka, a distributed streaming platform, and how it fits in an Event-Driven Architecture. Bernd Rücker described how workflow engines can handle complex business processes, and discussed how Zeebe, a new highly scalable workflow engine, can be used with Kafka.
-
In a Serverless World, We Still Need State
Today there is a large push in enterprise architecture towards serverless architecture. Jonas Bonér argues that although he strongly believes in the serverless movement, the programming model should not focus only on stateless functions. We must also have a focus on state, allowing us to benefit from the advantages of serverless while building distributed general-purpose applications.
-
Build a Monolith before Going for Microservices: Jan de Vries at MicroXchg Berlin
Most developers don’t work at global large-scale companies like Netflix. Most developers work in much smaller companies with maybe up to 50 – 80 developers, Jan de Vries noted in his presentation at MicroXchg Berlin, where he argued that a properly built monolith in many cases is superior to a microservices based architecture. With a well-built monolith, it will also be easy to pull services out.
-
Creating Events from Databases Using Change Data Capture: Gunnar Morling at MicroXchg Berlin
When you store data in a database, you often also want to put the same data in a cache and a search engine. The challenge is how to keep all data in sync without distributed transactions and dual writes. One way is to use a change data capture (CDC) tool that captures all changes made. In a presentation at MicroXchg Berlin, Gunnar Morling described Debezium, an implementation of CDC using Kafka.
-
A Critical Look at Event-Driven Systems: Bernd Rücker at QCon London
There is currently a hype in adoption of event-driven systems. Sometimes they are almost seen as the “magic thing” in our strive for decoupled systems, Bernd Rücker noted at the recent QCon London 2019. In his presentation he took a critical look at three common hypotheses around event-driven systems: events decrease coupling, Orchestration needs to be avoided, and Workflow engines are painful.
-
The Importance of Event-First Thinking
For global businesses to meet today’s architectural challenges with constant change and extreme scale, we need to go back to the basic principles of system design. The common element in the problems we face is the notion of events driving both actions and reactions, Neil Avery writes in a series of blog posts describing why events are so important and the advantages of an event-first approach .
-
Microsoft Announces Several Updates to Azure Event Grid
Microsoft has announced multiple updates to Azure Event Grid, which allows for creating event-driven application architectures. The announcement includes features around retry policies, dead lettering capabilities, Azure Storage Queues and Hybrid Connections as a destination for events, and a manual validation handshake.
-
Are Frameworks Good or Bad, or Both?
Preferring frameworks or libraries is somewhat controversial, Frans van Buul, Evangelist at AxonIQ, the company behind Axon Framework, writes in a recent blog post. Many argue in the favour of libraries but Van Buul thinks that a framework can be very valuable when building business applications. He believes this to be especially true for applications based on CQRS, DDD and event sourcing.
-
Experiences Moving from Microservices to Workflows at Jet.com
The Order Management System (OMS) at Jet was originally developed using a collection of microservices orchestrating tasks. As the company grew, the challenges with this architecture also grew until they decided to build a new workflow-based platform. In a blog post, James Novino at Jet describes the challenges with their old system and an overview of the new platform.