Even though Kafka provides convenience methods to persist the committed offsets for a given consumer group, you’re not required to use that behavior and can write your own if you feel the need. Even so, the use of Kafka the way you’ve described it is a bit awkward for the use case as each client … Read more
Message Oriented protocols send data in distinct chunks or groups. The receiver of data can determine where one message ends and another begins. Stream protocols send a continuous flow of data. Here is an example with mobile phones. Text messages would be a message oriented protocol as each text message is distinct from the other … Read more
Messaging tends to concentrate on the reliable exchange of messages around a network; using queues as a reliable load balancer and topics to implement publish and subscribe. An ESB typically tends to add different features above and beyond messaging such as orchestration, routing, transformation and mediation. I’d recommend reading about the Enterprise Integration Patterns which … Read more
An overview – A protocol – A set of rules. AMQP – AMQP is an open internet protocol for reliably sending and receiving messages. MOM (message-oriented-middleware) – is an approach, an architecture for distributed system i.e. a middle layer for the whole distributed system, where there’s lot of internal communication (a component is querying data, … Read more
This is a great question. The main uses of messaging are: scaling, offloading work, integration, monitoring, event handling, routing, networking, push, mobility, buffering, queueing, task sharing, alerts, management, logging, batch, data delivery, pubsub, multicast, audit, scheduling, … and more. Basically: anything where you need data but don’t want to make a database request. (Caching is … Read more