Eventuate.io has formally released a new version of the Eventuate platform. It ships with a host of new significant features including the addition of support for Micronaut to the Eventuate Tram/Local frameworks, upgrade to Java 14 and Spring Boot 2.2.6, enhanced developer tooling using a new Spring Boot-based starter service and finally greatly improved performance and observability metrics for the Eventuate CDC component.
The Eventuate platform caters to the problem of management of distributed data in a microservices-based architecture. It is split into two main components, a set of frameworks -> Eventuate Tram/Eventuate Local and infrastructure -> Eventuate CDC. The Eventuate Tram framework is used for microservices that rely on traditional persistent models (e.g. JPA/JDBC) and can be easily added to existing microservices applications with minimal changes to the code base. The Eventuate Local framework, on the other hand, is used for microservices that rely on the Event Sourcing persistent model. The Eventuate CDC (Change Data Capture) component performs the complex task of orchestrating operations between the various physical resources (databases / message brokers) within a microservices landscape.
Eventuate Tram/Eventuate Local frameworks now include support for using Micronaut in addition to Spring Boot. The example applications have been updated to reflect the support for Micronaut. This includes the Eventuate Tram Customers and Orders - Micronaut (using choreography) and Eventuate Tram Sagas Customers and Orders - Micronaut (using orchestration).
The current Java/Spring Boot support for both frameworks has been upgraded to Java14 and Spring Boot - 2.2.6. The frameworks continue to provide support for popular databases (MySQL/Postgres) and message brokers (Apache Kafka, ActiveMQ, RabbitMQ and Redis Streams).
The Eventuate CDC Service now has improved performance capability in addition to enhanced observability for the service including health check endpoints and service metrics based on Prometheus. It continues to support all major databases and message brokers.
According to Chris Richardson, the founder of Eventuate.io, the fundamental premise of the platform is to help tackle the problem of distributed data management, which is quite prevalent in microservices-based architectures. Patterns such as transactional messaging, outbox patterns, CQRS, sagas, and event-driven microservices have emerged in recent times as solutions. Implementing these patterns are complex and require a high degree of investment and effort by enterprises. The platform aims to plug that gap by offering a complete suite of tools and techniques which provide robust implementations of these patterns, freeing up the developers to focus on what they do best, i.e. implementing business logic.
Richardson further states that his experience in helping enterprises migrate to microservices led to the realization of the value of enabling the platform to be used with an enterprise’s current infrastructure in place, e.g. MySQL/Postgres databases and Kafka/RabbitMQ message brokers. These are familiar, proven and scalar technologies which significantly lower the adoption barrier for the platform.
The platform is now in its fifth year of existence and has evolved into a mature platform with multiple features incorporated over the years. Richardson mentions that the team is hard at work to continue to add new features that make it easier for developers to implement microservices. There will also be expansion of support for the current frameworks, including releasing NodeJS support.
This new release adds to the growing trend of mature platforms like AxonIQ, vLingo, and EventStoreDB that are being made available to easily implement event-driven microservices, event sourcing based architectures, sagas, CQRS patterns, and domain-driven-design techniques.