[Eureka] Namespace Architecture
This diagram compares two namespaces used for deploying the FOLIO and Eureka systems, showing different components and how they interact.
On the left side, we have the FOLIO deployment, which is more straightforward. It starts with the Tenant UI bundle, set up as a Replica-set. This UI bundle connects to Okapi, which is also a Replica-set and serves as a gateway for FOLIO's backend. The backend is similarly a Replica-set, showing the system values redundancy and stability. Below the backend is the FOLIO edge, another Replica-set, likely providing an interface to external systems or services.
These main components connect to a range of stateful services like PostgreSQL, which has a list of databases, Opensearch for search functionality, and Kafka for streaming and messaging. Each of these is a Stateful-set, meaning they are designed to handle data persistently.
On the right side, the Eureka deployment is more complex. It also has a Tenant UI bundle as a Replica-set but adds a Keycloak Stateful-set for authentication and Kong as a Daemon-set, probably for managing microservices traffic. The Eureka management application is a key component shown as a Replica-set, which implies it's important for the system's resilience.
The FOLIO backend module here has a Sidecar attached, for discovery and proxy. The FOLIO edge module also appears with a Sidecar, and they both connect to the same set of stateful services (PostgreSQL, Opensearch, Kafka) as the FOLIO deployment, but they're also interconnected with Keycloak and Kong, showing more integration points.
The connections between services are more intertwined in the Eureka deployment, indicating a more complex interaction between components. This could reflect additional features or a higher level of customization compared to the FOLIO deployment.
In summary, the diagram shows two different namespace setups for deploying systems, with Eureka having a more complex arrangement involving additional components and connections compared to FOLIO.