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

The lecture introduces event driven architecture, explaining its importance and how it enables applications to respond to events. It covers the concept of events in computing, including user and system generated events, and demonstrates using Windows Event Viewer as an example. The benefits of event driven architecture, such as improved responsiveness and flexibility, are discussed. The lecture also explores how Azure services like Event Hub and Service Bus support event driven applications. Finally, it concludes with a recap of the key points.

What is an event in the context of computing?

• A system error that cannot be logged

• A user action that has no impact on the system

• An identifiable occurrence significant to system hardware or software

• A random occurrence with no significance

Which tool is used in Windows to view event logs?

• System Monitor

• Event Viewer

• Control Panel

• Task Manager

What action can be taken when an application hang event occurs?

• Attach a task to respond to the event

• Restart the computer

• Ignore the event

• Uninstall the application

How can event-driven processing benefit an application?

• By reducing system resources

• By improving responsiveness and flexibility

• By making the application slower

• By increasing the complexity of the application

What can be done if an application does not use Event Viewer?

• Disable event logging

• Write a program to process log files and create events

• Manually log events in a text file

• Ignore the events

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

• Azure Virtual Machines

• Azure Event Hubs

• Azure Blob Storage

• Azure SQL Database

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

• The event is sent to a different database

• The system crashes

• The event is stored in a storage queue for later processing

• The event is discarded