InfoQ Homepage Event Driven Architecture Content on InfoQ
-
Microservices: Usage Is More Important than Size
Using size for defining microservices is useless when determining a service responsibility, Jeppe Cramon states in a series of blog posts explaining his view on microservices and the coupling problems he finds in synchronous two-way communication.
-
Scalability in a Reactive World
We have to maximize locality of reference and minimize contention to make systems scale, Jonas Bonér, creator of the Akka project, stated in a recent presentation about scalability in reactive systems. By using a share nothing architecture, build on an event-driven foundation and adhering to core principles that have been proven to work for ages we can write really scalable systems.
-
Udi Dahan on Event-Driven Architecture and Loosely Coupled Systems
We should build systems more loosely coupled to achieve properties like robustness, resilience and scalability, Udi Dahan emphasizes in a recent presentation discussing how we can model our systems using more event-driven and asynchronous patterns and some of the challenges developers face when introducing these principles and patterns into development.
-
Akka Actors vs. Java EJBs from a High-Level Concurrency Perspective
There are both commonalities and some differences when comparing architectural principles and coding styles in Akka Actors and Java EE 7 Enterprise JavaBeans, specifically stateless session beans and JMS message-driven beans, Dr Gerald Loeffler concludes in a recent introductory talk when explaining and comparing the three approaches from a high-level concurrency view.
-
CQRS Framework Axon 2.1 with Increased Event Handler Support and Performance Improvements
Version 2.1 of CQRS framework Axon supports annotations and ordering of event handlers, a new conflict resolution together with performance improvements. The recently released version also adds compatibility with OSGi.
-
Greg Young on Using Complex Event Processing
Complex Event Processing, CEP, can be very useful for problems that have to do with time e.g. querying over historical data when you want to correlate things that have happened at different times, Greg Young explained in a recent presentation.
-
Vaughn Vernon: Reactive Domain-Driven Design
Vaughn Vernon, author of Implementing Domain-Driven Design, recently talked about using Scala and the Actor Model implementation Akka together with Doman-Driven Design as a means to remove some of the architecture overhead typically found in event-driven or hexagonal architectures.
-
Pivotal's Reactor Goes GA
This week, Pivotal released version 1.0 of its project Reactor for general availability. Reactor provides low-level abstractions for an event-driven, reactive programming model, and is a component member of the Spring IO Platform in its "IO Foundation" layer.
-
Implementing Hexagonal Architecture using Life Preserver and Spring Framework
Russ Miles recently shared some thoughts and ideas about the needs for adaptability in a system and how his implementation of the Hexagonal Architecture can help in achieving this. He used a Java and Spring based application to exemplify how such a system can be implemented.
-
Event Store 2.0 Released with Security Support and the Projections Library in Beta
Version 2.0 of the Event Store, (an Event Source based persistence engine), was released last week with support for security, allowing for lock down of the Event Store and setting up Access Control Lists on event streams. The Projections library is now in beta and more documentation has been added.
-
NServiceBus 4.0 with support for RabbitMQ and ActiveMQ
Version 4.0 of NServiceBus, a service bus for .NET, has just been released with support for RabbitMQ and ActiveMQ in addition to MSMQ. Support for using database tables as queues has also been added, and performance for the MSMQ transport has been significantly improved. According to Udi Dahan, the founder of NServiceBus, this is the biggest release ever.
-
Greg Young on Documents and Processes as an Alternative to Events
Not all systems are based on events or facts. In some problem spaces events make complete sense; they are about facts that are happening over periods of time. But a lot of systems are instead focused on information that flow through a process, Greg Young explained at DDD Exchange Day in London last week, using handling of a mortgage application inside a bank as an example.
-
Vaughn Vernon on the Actor Model and Domain-Driven Design
To take advantage of the great concurrency opportunities the new multi-core machines gives us we should use a programming model that helps us achieve this, and the Actor model gives us a number of tools for doing that, Vaughn Vernon stated at this year’s DDD Exchange Day in London.
-
Build Simplicity into a System with Simple Event-Driven Components
Use events for interactions between small business components to bring simplicity to a system’s architecture, Russ Miles suggests in a recent presentation about simple event-driven components, as a follow-up on his talk a month earlier where he laid the architectural ground for his ideas about simplicity.
-
New C# based CQRS Tutorial available
A new CQRS, Command Query Responsibility Separation, C# based Starter Kit to help developers get up and running with CQRS on .NET has been developed, not as a framework, but as a tutorial for developers interested in learning about CQRS, and as a possible starting ground for a CQRS based system.