Event-driven solution is still a hot topic
Recently I have to justify why Event-Driven Architecture is still a hot topic on the current market: as I work with a lot of companies in financial, healthcare or retailer industries, I see strong adoption for loosely coupled, event-driven microservice solutions, with new data pipeline used to inject data to modern data lakes, and the adoption of event backbone technology like Apache Kafka, or Apache Pulsar. With my team, we are working on reference architectures, reference implementations, and first-of-a-kind solutions based on event-driven implementations. Over the last year, this space is evolving a lot with the adoption of serverless, knative eventing, cloud-native technologies, microprofile 3.x messaging... In this blog, I want to introduce our EDA work and references to some assets you may be able to leverage for your own project. I will continue future blogs to present in more detail some of those assets and best practices we have to develop for customer engagements. Event-drive