You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Microservice pattern: Server-side service discovery #2686
Implement the Server-Side Service Discovery design pattern for the project. This pattern helps in dynamically locating services within a microservices architecture, enhancing the system's scalability and flexibility.
Main Elements of the Pattern:
Service Registry: A central repository that holds the network locations of service instances.
Service Provider: Services register their instances with the service registry.
Service Consumer: Consumers query the service registry to find available service instances.
Load Balancer: Directs service requests to available service instances based on a load-balancing strategy.
Health Check: Ensures that only healthy service instances are registered and available for service discovery.
Service Registry Setup: Implement a service registry (e.g., Eureka, Consul) to manage the dynamic locations of service instances.
Service Registration and Discovery: Ensure that services can register themselves with the service registry and that consumers can discover these services.
Load Balancing and Health Checks: Integrate load balancing and health checks to maintain the availability and reliability of the service instances.
This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.
Activity
lokytech5 commentedon Oct 16, 2023
can you assign me this
lokytech5 commentedon Oct 19, 2023
Please specify if I can use Spring Boot to implement the design or core Java.
iluwatar commentedon Oct 22, 2023
Yes, Spring Boot can be used. It has been used in some other patterns as well.
lokytech5 commentedon Oct 22, 2023
currently on it
stale commentedon Dec 22, 2023
This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.
4 remaining items
iluwatar commentedon Jun 6, 2024
The issue is currently unassigned. We are open for proposals 😀
AmanH7618 commentedon Dec 29, 2024
@iluwatar Can you please assign this to me?
github-actions commentedon Mar 13, 2025
This issue is stale because it has been open 60 days with no activity.
krupaliw commentedon Oct 6, 2025
@iluwatar can you please assign this to me?
RitikaMathur19 commentedon Oct 16, 2025
Am working on this will share the PR soon. @iluwatar please assign it to me