This will be the third installment of our Azure series of Hands On Labs.
Please be aware that for the entire lab series you will need an Azure subscription of some kind if you want to follow along. Here are your options:
• Corporate account
• Visual Studio Subscription (previously MSDN)
• Partner Action Pack
• Pay as you go
You will also need Visual Studio Community or Enterprise - 2017 or 2015 w/update 3. Please have this on your system before coming to the meeting - our bandwidth is limited...
There will be seats for 30 in the main room. We will simulcast to the other rooms for a total of 75 seats.
What we'll be doing...
Azure Event Hubs is a hyper-scale telemetry ingestion service that collects, transforms, and stores millions of events. As a distributed streaming platform, it gives you low latency and configurable time retention, which enables you to ingress massive amounts of telemetry into the cloud and read the data from multiple applications using publish-subscribe semantics. Use the Event Hubs Archive feature, which allows a single stream to support real-time and batch based pipelines, and reduces the complexity of your solution. Build for today’s batch processing on a platform that supports tomorrow’s real-time analytics and processing. Event Hubs Archive is the easiest way to load data into Azure.
Service Bus is a multi-tenant cloud service that provides modern message queuing concepts implemented in the Microsoft Cloud as platform as a service:
• Queues, which allow one-directional communication. Each queue acts as an intermediary (sometimes called a broker) that stores sent messages until they are received. Each message is received by a single recipient.
• Topics, which provide one-directional communication using subscriptions-a single topic can have multiple subscriptions. Like a queue, a topic acts as a broker, but each subscription can optionally use a filter to receive only messages that match specific criteria.
• Relays, which provide bi-directional communication. Unlike queues and topics, a relay doesn't store in-flight messages; it's not a broker. Instead, it just passes them on to the destination application.
Lab1 - https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-bus-messaging%2Fservice-bus-dotnet-get-started-with-queues&data=02%7C01%7Crross%40microsoft.com%7C80e45aaf49304c2a78c308d4acdf5909%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636323522653120920&sdata=dT7HexSHJ6nx%2FltL%2B7aoG7o3WFbDo%2F4BiLlkEfADzd0%3D&reserved=0)
Lab2 - https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-how-to-use-topics-subscriptions (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-bus-messaging%2Fservice-bus-dotnet-how-to-use-topics-subscriptions&data=02%7C01%7Crross%40microsoft.com%7C80e45aaf49304c2a78c308d4acdf5909%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636323522653120920&sdata=Tx9a2yK%2BTgNd%2FTNY4aRw9NJ2Gsi4cS8%2BaTEfg7Qi0X8%3D&reserved=0)