Learn Azure Serverless Functions in a Weekend - Event-Driven Architecture

This lecture introduces event driven architecture, explaining its importance and how it operates. It defines events in computing, differentiating between user and system generated events. A practical example using Windows Event Viewer demonstrates task scheduling based on events. The lecture highlights the benefits of event driven architecture, such as improved responsiveness and flexibility. It also explores how Azure services like Event Hub and Function App facilitate event driven applications. The session concludes with a summary of key points discussed.

What is an event in the context of computing?

• An identifiable occurrence significant to system hardware or software

• A user-generated action only

• A random occurrence with no significance

• A scheduled task in a calendar

Which of the following is an example of a system-generated event?

• Mouse click

• Keystroke

• User login

• Service start event

What tool is used in Windows to view event logs?

• Command Prompt

• Control Panel

• Event Viewer

• Task Manager

In the example provided, what action is taken when an application hang event occurs?

• The computer restarts

• The event is logged only

• A program is started

• The event is ignored

How can event-driven architecture benefit existing applications?

• By extending them in a flexible, non-invasive manner

• By making them more complex

• By making them less responsive

• By reducing their functionality

Which Azure service is used to handle events in an event-driven architecture?

• Azure Event Hub

• Azure Virtual Machines

• Azure Blob Storage

• Azure SQL Database

What happens if a Function App fails to store an event in Cosmos DB?

• The event is discarded

• The event is saved to a storage queue for later processing

• The system crashes

• The event is sent to another database