Last year i was developing a message queue based application for our company to be used by different other products/application.Since it's purpose was to be very scalable and also to be used by various other application, so we named it Universal Message Queue (UMQ).
Why UMQ came to the picture?
Earlier database was used as queue for certain scenario. But Database is not a good choice for huge queuing functionality. A heavy loaded database with additional queuing functionality will affect the performance of an application. Database should not be used for queuing purpose because of following:
To overcome the above issues, UMQ is good choice. UMQ is a generalized message queue system.
It is based on rest services. Beside eliminating the issues of database as a queuing system, UMQ
has the important additional features that are useful in different scenario for various application as
stated below.
Some of the major components that were used for the UMQ are RabbitMQ and Redis.
Truly speaking we have done lots of poc & rnd with various opensource message Queue's before developing this internal product,but RabbitMQ was able to full-fill our above needs very well.
Some of the fetaures of RabbitMQ are very well, like Routing logic based on Exchange and Queue mechanism, Prioity(through its Plugin) ,Negative Acknowledgement(NACK) with/without Requeing and Delay or Schedule Message delivery.
So in the next tutorial,i will give you the idea of Delay/Schedule message delivery along with how to implement the logic through java.
Why UMQ came to the picture?
Earlier database was used as queue for certain scenario. But Database is not a good choice for huge queuing functionality. A heavy loaded database with additional queuing functionality will affect the performance of an application. Database should not be used for queuing purpose because of following:
- Database inherently does not support queue functionality
- Using Database as queue increases load on the database, hence affect the overall application performance.
- Implementing some new functionality of queue (such as priority, Delay, Tracking etc) through database are complex and not well proven.
To overcome the above issues, UMQ is good choice. UMQ is a generalized message queue system.
It is based on rest services. Beside eliminating the issues of database as a queuing system, UMQ
has the important additional features that are useful in different scenario for various application as
stated below.
Some of the major components that were used for the UMQ are RabbitMQ and Redis.
Truly speaking we have done lots of poc & rnd with various opensource message Queue's before developing this internal product,but RabbitMQ was able to full-fill our above needs very well.
Some of the fetaures of RabbitMQ are very well, like Routing logic based on Exchange and Queue mechanism, Prioity(through its Plugin) ,Negative Acknowledgement(NACK) with/without Requeing and Delay or Schedule Message delivery.
So in the next tutorial,i will give you the idea of Delay/Schedule message delivery along with how to implement the logic through java.
No comments:
Post a Comment