Eureka
A service registry enabling microservices to register dynamically, discover peers, handle failovers, and communicate without hardcoded hostnames and ports
&
| + | Service Registration | Enables microservices to register their network locations in the registry so that other services can locate them |
|---|---|---|
| + | Service Discovery | Allows microservices to query the registry for network locations of services so that they can connect during runtime |
| + | Client-Side Load Balancing | Delivers a list of service instances to clients that then choose an instance using a load selection process, thereby using registry data with client libraries to distribute requests among service instances so that workload is spread during client calls |
| + | Peer Replication | Enables registry nodes to exchange updates on registered services with one another to maintain a shared state of records |
| + | Heartbeat Mechanism | Requires microservices to send periodic signals to the registry to confirm their operational status, which helps remove entries for absent services |
| + | Self-Preservation Mode | Retains service records during network issues when heartbeat signals are absent, preventing the removal of services during connectivity issues that may still be in operation |
| + | Instance Metadata Registration | Registers each service instance with network details such as IP, port, and status URL to support system diagnostics and routing |
| + | Registry Replication | Allows registry nodes to replicate registration data among themselves so that multiple servers maintain a shared set of service records |
| + | REST API Endpoints | Offers HTTP endpoints for registering, discovering, and managing services, which enables integration with external systems |
| + | Service Health Monitoring | Provides endpoints to check the health status of registered service instances, which aids in system monitoring and operational actions |
| + | Caching of Registry Data | Stores queried registry data on clients to reduce the number of network calls, thereby improving access efficiency |
| + | Configuration Support | Uses configuration files or property sources to set registry parameters so that deployments can be tailored for each environment |
| + | Spring Cloud Ecosystem Integration | Operates within the Spring Cloud environment to enable communication and coordination among microservices using a shared registry |
| + | Zone Labeling | Allows service instances to register with zone or region labels so that discovery can be performed based on location segments |
| + | Failover Handling | Addresses registry operation during service restarts or network interruptions so that registry functionality continues across failures |
| + | Registration Update | Refreshes service registration details on a set schedule so that the registry maintains up-to-date records of active services |
| + | Identifier Convention | Uses application names as service identifiers during registration to support a unified naming approach in microservice systems |
| + | Query Customization | Provides options to filter registry queries using parameters so that users can retrieve specific sets of service records as needed |
| + | Dashboard Interface | Offers a web interface that displays service registration records and registry status so that system operators can oversee system operation |
| - | Limited Flexibilty | The registry is built to function with a defined set of tools (the Netflix OSS stack). This structure makes it less flexible when integrating with alternative frameworks. |
| - | Infrastructure Management Requirement | Demands a registry cluster setup for high availability, introducing extra components that must be maintained |
| - | Stale Instance Handling | Uses a self-preservation mode that may retain service information that is no longer valid, reducing the accuracy of the registry |
| - | Vendor Lock-in | Increases reliance on the Netflix OSS ecosystem, making it difficult to transition to alternative service discovery solutions. |
Social
Not available, but we appreciate help! You can help us improve this page by contacting us.
System Requirements
Not available, but we appreciate help! You can help us improve this page by contacting us.
Ratings
Not available, but we appreciate help! You can help us improve this page by contacting us.
Repository
License
Categories
Alternatives
Virtualization Tool
Buildah Minishift K3D Kind minikube Consul by HashiCorp Proxmox Virtual Environment Kubernetes VMware Desktop Hypervisor Podman Docker Vagrant by HashiCorp QEMU Apache Mesos VirtualBox
Cloud Computing
Kubecost Pulumi IaC Infracost Terraform by HashiCorp Velero Apache Hadoop Apache Mahout Apache Spark
Buildah Minishift K3D Kind minikube Consul by HashiCorp Proxmox Virtual Environment Kubernetes VMware Desktop Hypervisor Podman Docker Vagrant by HashiCorp QEMU Apache Mesos VirtualBox
Cloud Computing
Kubecost Pulumi IaC Infracost Terraform by HashiCorp Velero Apache Hadoop Apache Mahout Apache Spark