In the configuration, our applications behave as consumers that communicate with each other to complete processes. They use a JSON format to send and receive messages. Consumer groups are used to scale our applications and share the same identifier. For example, when two model controllers coexist, each one is a consumer and they both belong to the same consumer group.
A topic is the data structure Kafka uses to store and distribute messages. Topics organize messages in partitions. Consumers are attached to different topics. When a topic receives a message, it sends it to a consumer group. Just one of the group’s consumers receives the message. The consumer array contains all connections receiving messages from a topic. Learn more about topic configuration here.
The groups object
{
"teamState": "",
"teamId": "",
"consumer": []
}
Parameter
Type
Description
teamState
string
The team’s status. Values can be Stable (the consumers are ready to receive messages), Dead (a consumer has an error), Empty (it doesn’t have any consumers), PreparingRebalance (it’s distributing partitions to new consumers), CompletingRebalance (it’s completing the distribution), and Unknown.