Azure Event Grid overview

1. Azure Event Grid overview

In this video, you'll learn the fundamentals of Azure Event Grid and how it's used in event-driven architecture.

2. Event Grid & event-driven architecture

You'll walk through the core concepts of Event Grid, why event-driven architecture matters, and how this approach can transform how applications interact. While you will connect Event Grid to Azure Function applications as both the source of events and event consumer, the principles will apply to connecting other types of apps, such as other Azure services, external devices, such as phones, sensors and wearables, and so on. Event Grid can facilitate communication between a wide range of services.

3. Event-driven architecture

Now, let’s connect this to the broader idea of event-driven architecture and how Event Grid enables it. In an event-driven architecture, the system responds to events as they occur. Events are shared between independent services. An event emitted by one service triggers work in another. Typically, each service acts as either an event generator (the source) or an event handler (the target). A message broker, like Event Grid, connects generators with handlers. Its efficient, scalable design supports real-time processing and immediate response.

4. Outsourcing long-running tasks

Another way event-driven architecture makes applications fast is by outsourcing long-running tasks to external services, so they are done asynchronously and don't block the main thread. Imagine a situation where you received a job offer with a link to accept it. You click on the link and the application responds right away. This is because all it did was to make a small and fast update to the database, recording the fact that you accepted the offer. All other processes, like generating contract, doing background checks, etc., were outsourced to external services via Event Grid.

5. Case study: document upload

Let’s look at a realistic use case I’ve worked with. Imagine a banking app. A customer applies for a loan. The loan agreement is issued by the bank and uploaded to the server using Azure Blob Storage.

6. Case study: document upload

When the document is uploaded, Event Grid triggers an event. Two subscribers handle it, both implemented as Azure Functions. One function sends a notification to the customer's device. The other logs the date and time of the upload in a database.

7. Case study: document upload

Thanks to Event Grid and an event-driven design, the customer sees that the loan agreement is ready right away, and the bank records the event for future auditing.

8. Event Grid overview

We talked about how event grid enables event-driven architecture. Now, lets talk more about what it is. In a nutshell, it is an Azure service that enables real-time, event-driven communication between Azure services and external third-party components. It does this by routing events to various destinations, which you’ll see shortly. Its architecture allows events to be processed quickly. It’s designed to be reliable and automatically scales to handle more or fewer events as needed, without you managing servers.

9. Let's practice!

Let's practice this!

Create Your Free Account

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.