![]() ![]() First of all, even if the size of queue can be very large, the maximum TTL (Time To Leave) of a message is 7 days. Of course there are also some limitations that we need to take into account. The maximum size of a message is 64 KB, but in combination blobs we can have messages that reach 200 GB. The only limit in this case is the bandwidth that can limit the number of concurrent clients. Because of this, we have the ability to store large amounts of data in queues, without thinking about the size of the queue.Īnother benefit of this type of queue is the number of concurrent clients that in theory is unlimited. Using Azure Storage Queues we can have a queue that has 200 TB. ![]() When I say a lot, imagine queues that can reach not 1 GB, not 1TB and not 10TB. This messaging system is part of Azure Storage and allows us to store a lot of messages in the same queue. The messaging solutions that will be discussed in this post are: For different use cases we may need to use different messaging systems, based on our needs. ![]() In the end of this post we will try to find a perfect messaging system that can be used in any situation. Once we understood each messaging system, we will compare them one by one. For each messaging system we will try to identify its strengths and when we should use it. In this post we will look at different messaging systems that are offered by Microsoft Azure. In an IoT era, where every day the number of devices that are connected to the internet increases drastically, we need to find different communication mechanisms.īecause we cannot control when a device is connected to the internet and ready to receive our package, we need to find different ways to communicate with it. But sending a message in a reliable and secure way can be a pretty hard job. In theory, sending a message over a wire to another device is a simple task. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |