Skip to content

Microservice pattern: Server-side service discovery #2686

Open

Description

@iluwatar

Description

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:

  1. Service Registry: A central repository that holds the network locations of service instances.
  2. Service Provider: Services register their instances with the service registry.
  3. Service Consumer: Consumers query the service registry to find available service instances.
  4. Load Balancer: Directs service requests to available service instances based on a load-balancing strategy.
  5. Health Check: Ensures that only healthy service instances are registered and available for service discovery.

References

Acceptance Criteria

  1. Service Registry Setup: Implement a service registry (e.g., Eureka, Consul) to manage the dynamic locations of service instances.
  2. Service Registration and Discovery: Ensure that services can register themselves with the service registry and that consumers can discover these services.
  3. Load Balancing and Health Checks: Integrate load balancing and health checks to maintain the availability and reliability of the service instances.

Activity

  1. converted this from a draft issue on Oct 15, 2023
  2. lokytech5 commented on Oct 16, 2023

    @lokytech5

    can you assign me this

  3. moved this from Todo to In Progress in Java Design Patterns projecton Oct 17, 2023
  4. lokytech5 commented on Oct 19, 2023

    @lokytech5

    Please specify if I can use Spring Boot to implement the design or core Java.

  5. iluwatar commented on Oct 22, 2023

    @iluwatar
    OwnerAuthor

    Yes, Spring Boot can be used. It has been used in some other patterns as well.

  6. lokytech5 commented on Oct 22, 2023

    @lokytech5

    currently on it

  7. stale commented on Dec 22, 2023

    @stale

    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.

  8. added
    status: staleissues and pull requests that have not had recent interaction
    on Dec 22, 2023
  9. 4 remaining items

  10. iluwatar commented on Jun 6, 2024

    @iluwatar
    OwnerAuthor

    The issue is currently unassigned. We are open for proposals 😀

  11. AmanH7618 commented on Dec 29, 2024

    @AmanH7618

    @iluwatar Can you please assign this to me?

  12. moved this from Todo to In Progress in Java Design Patterns projecton Jan 11, 2025
  13. github-actions commented on Mar 13, 2025

    @github-actions

    This issue is stale because it has been open 60 days with no activity.

  14. moved this from In Progress to Todo in Java Design Patterns projecton Mar 18, 2025
  15. krupaliw commented on Oct 6, 2025

    @krupaliw

    @iluwatar can you please assign this to me?

  16. RitikaMathur19 commented on Oct 16, 2025

    @RitikaMathur19

    Am working on this will share the PR soon. @iluwatar please assign it to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions