Two weeks ago, we announced the GA of Streams Messaging Manager (SMM) 1.0 to cure enterprises of their Kafka Blindness. We discussed how SMM addresses the needs of three groups in the enterprise: Platform Operations, DevOps/Developers and Security/Governance teams. In this second installment of the SMM blog series, we focus on the DevOps/Developers persona and explain how SMM addresses their unique needs and use cases.
The DevOps / Developers persona is most interested in the entities (producers, topics, consumers) specific to their applications. So let’s assume we are on the DevOps team responsible for monitoring a streaming analytics application that is deployed in production based on this architecture.
The below table represents a set of needs/requirements/questions that a DevOps user might have when monitoring this application.
Lets walkthrough how SMM can answer these questions for DevOps/Developers.
In addition to the eight use cases defined above, one of the most critical and common use case for DevOps is to identify slow consumers. Slow consumers are defined as applications that cannot keep up with the rates at which producers generate data. This can result in apps not being able to identify actionable insights on time, etc. SMM makes it very easy to find slow consumers for a given topic through its intelligent filtering and sorting capabilities.
However, finding slow consumers is meaningless if the user is not able to quickly identify and understand what the consumer is doing to cause the lag so that it can be addressed. This bring us to one of the most powerful and differentiating features of SMM. With SMM’s Atlas Integration, the user is able to see metadata about consumer client application allowing the user to quickly understand why the consumer is slow to process. Key metadata about Kafka consumer application include visibility into what the consumer application is doing, where the consumer application is running, and what downstream systems the app is talking to.
The short video below showcases these powerful capabilities in SMM including:
SMM has clearly changed the game for enterprises that are struggling with Kafka operational and visibility challenges. Specifically, SMM enables the DevOps / Developer personas to achieve complete control and gain deep visibility into their Kafka flows and streams. DevOps can seamlessly work across multiple Kafka environments from a single SMM instance. In a future post, I will cover another awesome capability of SMM – its REST server. The entire SMM UI is driven by a powerful set of REST endpoints that are made available to the developer. This enables developers to integrate any enterprise applications like ticketing/application monitoring apps with SMM.
Register for our upcoming webinar “Curing Kafka Blindness with Hortonworks Streams Messaging Manager” on September 6th 2018. Dinesh and I will be showcasing the product in great detail with some exciting demos of the product as well. Join us!