{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Kafka Won’t Save Your Architecture If You Don’t Understand Coupling","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/552f54ec\"></iframe>","width":"100%","height":180,"duration":798,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/kafka-wont-save-your-architecture-if-you-dont-understand-coupling.\nMessage queues don’t magically decouple services. Here’s what Kafka changes, what it hides, and why “async” can still fail hard.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #system-design, #kafka, #operating-systems, #microservices, #distributed-systems, #rabbitmq, #system-resilience, #dead-letter-queues,  and more.\nThis story was written by: @wickedseal. Learn more about this writer by checking @wickedseal's about page,\n            and for more stories, please visit hackernoon.com.\nMany teams treat Kafka, RabbitMQ, or SQS as automatic solutions for decoupling and resilience. In reality, queues only reduce certain kinds of coupling while introducing new ones: hidden dependencies, ordering assumptions, retry semantics, duplicate delivery, stale events, and shared infrastructure risk. They also make failures harder to observe. Message queues are powerful tools, but they do not eliminate complexity — they move it.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}