The marketing team can listen for the Account Created event and act on it (for example, send promotional emails). When the event is raised, other teams can be alerted. You build the login workflow, and raise an event when a new user creates an account. Your team is in charge of the account creation and authentication process. For example, let’s say you are a developer at an ecommerce company and you are building a serverless ecommerce application. Decoupling event sources and event targets can greatly speed up development time, and it can simplify making changes to your application.ĭecoupling your application can allow for more seamless cross-team collaboration. The event source is what emits the event, and the event target is what subscribes to or receives the event. When you add new features to your applications, you raise new events and then decide on the event source and event target. This can enable teams to act more independently, because your services are loosely coupled. When you build applications with event-driven architecture, you decouple your event sources and event targets. Other components listen and decide what to do with it and how they would like to react. In event-driven architecture, each component of the application raises an event whenever anything changes. Events are JSON objects that tell you information about something that happened in your application. An event is something that happened in your application (for example, an item was put into a cart, a new order was placed). In event-driven architecture, services interact with each other through events.

Postman app events bus requester