3/24/2024 0 Comments Queue offer meansThey both provide 99.9999999% reliability and ensure successful message delivery within the valid period. The Performance Differenceīoth the Message Queue and the newer Message Service are blazing fast and globally scalable across the many Alibaba Cloud data centers. On the contrary, it would be a rather trivial affair if they were using the Message Service. Both saw great gains, companies in similar shoes would find that difficult or impossible to do if those components depended on the Message Queue. Which can be vital for the competitiveness of any application, for example Uber rewrote their Geolocation component from Python to Go while One Signal rewrote their entire application in Rust. What this means is that the newer Message Service removes the restrictions on what programming languages or frameworks you can use. The consumer can be any HTTP server, a browser via websockets, a mobile phone, an email address or even another Message Queue service! Another decisive differentiator is that the Message Service has the ability to push out message to consumers instead of waiting for them to pull the messages out of the queue. There are official SDKs of course, but these are mostly to add synthetic sugar to make using it easier. This opens the door to almost each and every programming language out there. This is a crucial differentiator implying that, so long as you can send a HTTP request, your application can use the Message Service. The newer Message Service product differs from the Message Queue in that it can speak HTTP. This means that both your producers and consumers must be written in one of those languages if you want official support. Currently, Alibaba Cloud supports Python, PHP. It also means you will most likely require an officially supported SDK to use it. This means you'll most likely require specific extensions enabled on your server to access these protocols. For example, the Message Queue can only speak over TCP or MQTT protocols. With those many years of development, the Message Queue had more community experience and expertise behind it, but it also comes with more legacy methods and restrictions. In September 2017, RocketMQ, the kernel engine of Alibaba Cloud Message Queue, became an Apache top-level project. The older, battled tested Message Queue has been integrated into the infrastructure of Alibaba Group for over 11 years and servicing Alibaba's 11-11 e-commerce sales event for over nine years. However, the major difference I've found is in how the message can be sent by the producer and consumed by the receiver. They both use and can execute this model with similar efficiency. To understand this, let's briefly look at the architecture of a message queue.Īt the very heart of both the Message Queue and Message Service is the design above. They almost sound like a paraphrase of each other, don't they? Well, as we'll see shortly, it's mostly because they are very similar products. Message Service is a message queuing and notification service that facilitates smooth transfer of messages between applications Message Queue is a distributed message queue service that supports reliable message-based asynchronous communication among microservices, distributed systems, and serverless applications. Many Cloud providers also offer managed message queues as a service and Alibaba Cloud has two of them namely the Message Queue and the Message Service.įrom their online descriptions. There are very many message queues out there, from RocketMQ, RabbitMQ, Apache Kafka, ZeroMQ, MosquitoMQ, and many more. You might have already come across the term message queues, if not I suggest you take a quick read over how they can greatly improve application reliability and scalability in a previous post Improving Reliability with Alibaba Cloud Message Service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |