AWS EventBridge - Event Logging and Storage in Event Driven Architecture

Question

I am currently developing an Event-Driven Architecture (EDA) system using AWS EventBridge, AWS SQS, and Java-based microservices. The system is operating effectively; however, I am exploring best practices for event logging to ensure comprehensive storage. The objective is to facilitate event replayability, allowing interested microservices to reconstruct the system's state at any given moment. 
Additionally, this logging strategy aims to support real-time status visibility for the monitoring and reporting services. I am seeking guidance on the recommended patterns and best practices for logging and storing events in an Event-Driven Architecture, specifically tailored to address these requirements

Answer

EventBridge supports events Archive and Replay, so if all you need is the ability to store and replay the events, it is built into the service. However, you do not have any access to the archive itself. If you need to get some other insights from the data, I would create an additional rule, that catches all events, and does something with them. In short, separate the two functions: For archiving use the built in system, and build what ever you need for the status visibility.

AWS EventBridge - Event Logging and Storage in Event Driven Architecture

相关内容