{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"How I Built a Kafka Consumer Framework So Teams Never Write Plumbing Twice","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/2f56f19d\"></iframe>","width":"100%","height":180,"duration":731,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/how-i-built-a-kafka-consumer-framework-so-teams-never-write-plumbing-twice.\nThat is my test for an internal framework: not whether the scheduling is clever, but whether the fifth team needs less documentation than the first.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #kafka-consumer, #consumer-worker-task, #generic-kafka-consumer, #plumbing, #kafka, #architecture, #internal-framework, #kafka-framework,  and more.\nThis story was written by: @navaprasadm. Learn more about this writer by checking @navaprasadm's about page,\n            and for more stories, please visit hackernoon.com.\nA framework for building Kafka consumers was created to simplify the process and provide a uniform experience across teams. The framework owns the plumbing, leaving teams to focus on writing the business logic in a single method.","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}