{"id":6821,"date":"2024-03-29T09:00:00","date_gmt":"2024-03-29T08:00:00","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=6821"},"modified":"2024-03-29T10:14:41","modified_gmt":"2024-03-29T09:14:41","slug":"decoupling-strategies-one-queue-to-rule-them-all","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/decoupling-strategies-one-queue-to-rule-them-all\/","title":{"rendered":"Decoupling strategies: one queue to rule them all?"},"content":{"rendered":"\n
Why decoupling?<\/h2>\n\n\n\n
Decoupling complex workloads is a practice that people sometimes undertake without a clear understanding of the advantages and risks. We frequently hear about modular applications built with microservices, where you can decide what to activate or deactivate without any impact on the other parts or that can scale infinitely.<\/p>\n\n\n\n