Why should we still use queues in an API landscape?
AUTHOR: ERWIN BEETS FOUNDER AND MANAGING PARTNER
The whole world is moving towards a simplified IT landscape based on REST. In this blog, we will explain why and when you should still use queues for your (Cloud) applications.
MODULAR SET UP OF YOUR APPLICATION
We advise you to think in advance about setting up your API or application in a modular way. By setting this modular design, you can easily scale in the future (in the cloud). The modular parts (with our adapters) are preferably linked to queues. These modular parts are decoupled so that they can be scaled in parallel and individually.
SCALING (IN THE CLOUD)
With high load or when offering large batches, it is important that your entire application can scale automatically. Because the components are decoupled by queues, they can be scaled in parallel and the rest of the application is not affected by a higher load.
An additional advantage of queues is that you can make your API or application transactional. Transactionality is used in (financial) processes, for example transactions, where it is important that the entire process is successfully completed. If something goes wrong at one of the steps in the process, the entire process (the individual transactions) must be reversed. You can achieve this by making your application modular and using queues.
MAKE YOUR API CLOUD INDEPENDENT
By not choosing a cloud native queuing solution, but for example (open source) ActiveMQ, your application remains Cloud Agnostic and you have no vendor lock-in for your application.
At WeAreFrank! we can build and manage high available, transactional and Cloud independent API solutions for you. We then build this solution with you, for example, ActiveMQ in combination with the open-source Frank!Framework. Would you like more information? Contact us below for a consultation.