A simple event-driven architecture explanation using PEGA App and AWS Kinesis data stream

In this post, let's understand a simple event-driven architecture example between a PEGA App and the AWS Kinesis data stream. Nowadays, where we have a plethora of applications within an organisation. Communication between the apps plays a vital role in architectural design. The conventional way of having APIs communication has its pros and cons. The disadvantages include — an API can become obsolete, and tightly coupled with the consumer and the service provider. As the applications grow, it is harder to maintain a huge set of APIs.

The event-driven architecture addresses this problem statement. Applications publish the event messages and other sets of applications who are interested subscribe to the events. It is up to the receiving system to process the event message. Event message data is extensible, fast, and reliant, and it is loosely coupled communication between the apps. Practical real-time examples include — Youtube, Facebook, Twitter, Google Maps, and GMail apps that generate the Live Location, and recent activity events to help the marketing systems to generate user-specific custom ads.

It is a publish and subscribe pattern similar to JMS — Java Messaging Service. But, with the latest event-streaming platforms like Apache Kafka, AWS Kinesis, Google Pub/Sub…