API vs MQ : if there is an API you don't need MQ, or will you make a front MQ for every API you're calling ?
This article is inconsiderate of the added complexity of MQs.
How is the payment processor given as example decoupled from the main process from let's say an e-commerce website using a MQ ?
If the payment processor isn't responding, the payment process on the main site is broken and a client can't purchase.
If many clients try again to pay, the MQ will be flooded and attain its max limit. How do you deal with added complexity and extra error handling of the MQ ?
Same question for integrating a new payment processor: with a different API or SDK to integrate, how would that not be the case with a MQ as stated in the article?
A MQ is simply a buffer when you need to scale up service consumption. But services with APIs don't need it, they do rate limiting and if they're down you should better set the status on your program and stop communicating until it's up again.
MQs are not automatic and this article is selling false promises and examples.
