Small, loosely coupled services that work together to achieve a common goal make up the architectural pattern known as “Microservices.” They can be added, removed, or upgraded without interfering with other applications because they operate independently. Microservices architecture has many advantages, such as easier deployment and testing, improved productivity, flexibility, and scalability. But it also has some drawbacks, as independently-run microservices require a seamless communication method to operate as one larger application. While using event-driven microservices, data can be consumed in the form of events, even before it is requested, allowing for real-time microservices communication.
This whitepaper will discuss how event-driven microservices work using a sample data exchange between Adobe Experience Manager and the Product MDM platform to demonstrate the design and architecture of an application composed of event-driven microservices using Apache Kafka and the Confluent Platform