In this session I will explain how I have implemented an event-driven architecture for connecting two critical systems with an language agnostic programming solution. Event-driven Architecture is a pattern that uses events to trigger and communicate between decoupled services and is common in modern applications built with microservices. Its key components are producers, routers and consumers. Some common use cases are: email dispatching, payment processing, fraud detection, background tasks, event subscriptions. Also some EDA characteristics are: flexibility, interoperability, language independent programming, scalability.

Some of the requirements for my software were:

- The admission app needs to send the accepted applicants to the academic app.
- The academic app needs to generate the required data for being able to get into enrollment process.
- The academic unique identificator needs to be present on the admission app for reporting.
- Avoid duplicity
- Avoid timeout errors
- Avoid complexity on the UI

For me, the best solution I could have found is to implement an event-driven architecture, it not only allowed me to scale my solution, but also to give end user the posibility to update all their reports with the latest information.