Registry

Overview

The Registry component of acts as a common service accessible to the other API Management - Local Edition components to discover other Local Edition component services, such as:
  • The host/port of the service
  • The properties of the Local Edition components
  • The bindings of the Local Edition components
The registry also outlines the Cluster-wide topology, including:
  • Cluster
  • Zones
  • Local Edition components
  • Properties and bindings of the Local Edition components
The Registry has the following core characteristics:
  • Redundancy available through the cluster
  • Works with the persistence layer (for example, Cassandra) to maintain a "current snapshot" of the cluster-wide topology.
  • Provides fine-grained REST APIs for each of the Local Edition components; for example, Cache, SQL DB, Traffic Manager. This includes:
    • Creation of Local Edition components
    • Listing of Local Edition components
    • Updates to Local Edition components
    • Receiving status and heartbeats from Local Edition components

The Registry is run as part of a Jetty process alongside the Cassandra process inside the NoSQL Local Edition component container. The proximity to Cassandra enables the Registry process to access Cassandra over 127.0.0.1:9042 host/port.

What's Inside

Java and Jetty Registry implementation.

Services

Registry Service

Resource Dependencies

  • NoSQL DB Binding
  • Log Producer Binding