Showing Post From Kafka
Schema registries in 2026: revisit Confluent Schema Registry, Apicurio Registry and Karapace before you ship another event schema
An event schema looks harmless in a pull request. A few fields, a namespace, maybe a default value. But once a producer starts writing with it, that schema is a contract with every consumer that reads the topic today and every consumer that will replay it next year.
Read moreRabbitMQ, NATS and Kafka queues: revisit your message queue before you add another broker
A health insurance company in Hyderabad processes claims through RabbitMQ: three nodes on 3.13 with classic mirrored queues, about 40 lakh messages a day, from claim documents to OCR, OCR results to fraud checks and approvals to payments.
Read moreKafka and Redpanda: revisit the choice before you treat them as the same bus
Many teams say “we run Kafka” when they mean “our services talk to a Kafka-compatible broker”. That shortcut was useful when one open source broker dominated the protocol.
Read more