ADS Control overview
Features
Arenadata Streaming Control (ADS Control) is a solution for managing Arenadata Streaming (ADS) clusters. It supports managing multiple ADS clusters.
For every integrated ADS cluster, the following can be performed in the ADS Control user interface:
-
assessment of the cluster and services state;
-
management of the cluster services functions.
Architecture
The architecture view of ADS Control is shown below.
ADS Control — the main and only service of the cluster, providing the full functionality of ADS Control. It includes the following built-in modules:
-
adscc-core — the main module of the service, created based on the Eclipse Vert.x asynchronous framework.
The module’s application consists of several reactive verticles, running in a single Vert.x instance. A verticle is a piece of code that acts as an event loop. Verticles interact with each other using events through the event bus after receiving a message or command. The event bus is also used to interact with various parts of the application and asynchronously delivers events to available verticles.
adscc-core exchanges signals with the user interface using its own REST API and provides interaction with the ADS services API and other external applications:
-
Kafka — displaying information about Kafka topics, brokers, and connected consumer groups; managing Kafka topics (creating, deleting, and configuring topics, writing and viewing messages).
-
Schema Registry — displaying information about available Avro schemas for topics; managing schemas (creating, registering, reading, and deleting schemas, verifying messages against a schema when writing, configuring schema compatibility).
-
Kafka Connect — displaying information about available Kafka Connect instances, existing connectors, and ready plugins; managing connectors (creation, start, stop, as well as migration of connectors).
-
Prometheus — can be connected to collect metrics via the built-in REST API endpoint of ADS Control.
-
Active Directory — user authentication and searching through LDAP/Active Directory binding.
-
-
adscc-cruise-control — the HTTP client module for connecting to Cruise Control. The module performs requests to configure parameters (goals, self-healing), obtain information about the current broker load, generate and accept proposals.
To use the module in an ADS cluster, the Kafka Cruise Control component of the Kafka service must be installed.
-
adscc-ranger-plugin — the module that is an Apache Ranger plugin, after activation of which the ability to manage access and user roles through policies and conduct audits appears.
To use the module, an ADPS cluster should be installed and integrated with the ADS Control cluster.