![]() If our app has different components, we can connect these components to the topics and queues that are in the namespace. A single namespace can contain multiple queues and topics, and namespaces can serve as application containers. This is a container for all messaging components. ![]() There are a few components that make up Service Bus: ![]() These messages can be in JSON, XML or just text format. Messages are raw data that can be sent asynchronously to Service Bus which can then be processed by another application that is connected to Service Bus. Service Bus is a fully managed enterprise-level messaging broker that allows applications to communicate with each other in a way that’s reliable and secure. My team primarily uses Event Hubs as our messaging broker, so it’s going to be interesting to learn what Service Bus and Queue Storage can offer.įor this tutorial, I’ll be developing a Azure Function app that will send messages to both Service Bus and Queue Storage (via separate POST requests). In this article, I’m going to be looking at the two technologies tested for developing message-based solutions, Azure Service Bus and Azure Queue Storage queues. ![]() Hopefully this will not just reinforce my learning, but also help others who may be taking AZ-204 themselves, or just want to learn something new. So in order to help my preparation for the exam, I plan to write a series of blog posts on each skill measured. I’ve been working with Azure in my day-to-day job for almost 2 years now, but taking a look at the exam skills outline, there are a few technologies on there that I’ve never touched before. In four weeks time, I plan to take my AZ-204 exam. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |