Service Discovery

@EnableEurekaServer
@SpringBootApplication
public class EurekaServerApplication {
}

// 1. Eureka Server (Service Registry)

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.cloud.netflix.eureka.server.EnableEurekaServer;

@SpringBootApplication
@EnableEurekaServer
class EurekaServerApplication {

  public static void main(String[] args) {
    SpringApplication.run(EurekaServerApplication.class, args);
  }
}

// application.properties (Eureka Server)
server.port=8761
eureka.client.register-with-eureka=false
eureka.client.fetch-registry=false


// 2. User Service (Eureka Client)

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.cloud.netflix.eureka.EnableEurekaClient;

@SpringBootApplication
@EnableEurekaClient
class UserServiceApplication {

  public static void main(String[] args) {
    SpringApplication.run(UserServiceApplication.class, args);
  }
}

// application.properties (User Service)
server.port=8081
spring.application.name=USER-SERVICE
eureka.client.service-url.defaultZone=http://localhost:8761/eureka


// 3. Calling Service using LoadBalancer

import org.springframework.web.bind.annotation.*;
import org.springframework.web.client.RestTemplate;

@RestController
class OrderController {

  private final RestTemplate restTemplate = new RestTemplate();

  @GetMapping("/order")
  public String getOrder() {

    String response = restTemplate.getForObject(
      "http://USER-SERVICE/users", String.class
    );

    return "Order Service -> " + response;
  }
}

// Output:
// Services register with Eureka Server
// Services discover each other dynamically

• 1 Automatically finds service locations.
• 2 Avoids hardcoded URLs.
• 3 Used in microservices systems.
• 4 Improves scalability.

• 1 Client-side discovery
• 2 Server-side discovery
• 3 Service registry (Eureka)
• 4 DNS-based discovery

• 1 Service registers with registry.
• 2 Registry stores service info.
• 3 Other services query registry.
• 4 Communication happens dynamically.

• 1 No hardcoded URLs.
• 2 Dynamic scaling.
• 3 Fault tolerance.
• 4 Easier maintenance.

• 1 Used in microservices architecture.
• 2 Used in cloud systems.
• 3 Used in distributed applications.
• 4 Used in scalable backend systems.
• 5 SaaS products use Service Discovery in Microservices in services, dashboards, background jobs, and API workflows.
• 6 ERP and banking systems apply Service Discovery in Microservices with validation, logging, review, and rollback plans.
• 7 E-commerce and healthcare platforms use Service Discovery in Microservices carefully because reliability and data correctness matter.

• 1 A Java program first evaluates the surrounding context, then applies the Service Discovery in Microservices rules to the current data.
• 2 The important mental model is input, transformation, result, and failure path.
• 3 In production, the same flow usually sits inside a larger layer such as a controller, service, repository, job, or UI component.

• 1 Choose the simplest implementation first, then measure real workloads.
• 2 Watch for repeated work inside loops, unnecessary allocations, and slow I/O in hot paths.
• 3 Prefer clear data structures and stable APIs before micro-optimizing syntax.

• 1 Treat external input as untrusted until it is validated.
• 2 Avoid hardcoded secrets and never print sensitive values in examples or logs.
• 3 Use established libraries for authentication, encryption, parsing, and database access.

• 1 Hardcoding service URLs.
• 2 Not using service registry.
• 3 Ignoring health checks.
• 4 Poor configuration of Eureka.
• 5 Skipping the small working example before adding framework code.
• 6 Ignoring null, empty, duplicate, and boundary inputs.
• 7 Mixing business logic, input handling, and output formatting in one place.
• 8 Using broad error handling that hides the real failure.
• 9 Forgetting to test the behavior after refactoring.
• 10 Adding clever code that future maintainers will struggle to read.

• 1 Use service registry like Eureka.
• 2 Enable health checks.
• 3 Use load-balanced calls.
• 4 Avoid hardcoded URLs.
• 5 Start with clear requirements and one minimal working example.
• 6 Use meaningful names that explain business intent.
• 7 Keep examples small enough to debug line by line.
• 8 Validate input at every trust boundary.
• 9 Handle errors explicitly and preserve useful context.
• 10 Prefer simple control flow over deeply nested logic.
• 11 Separate domain logic from I/O and framework code.
• 12 Write tests for normal, boundary, and failure cases.
• 13 Review security assumptions before production use.
• 14 Measure performance before optimizing.
• 15 Document non-obvious decisions close to the code or in project notes.
• 16 Use official documentation when behavior is version-specific.
• 17 Keep dependencies current and remove unused code.
• 18 Avoid hardcoded secrets, credentials, and environment-specific paths.
• 19 Log operational events without exposing sensitive data.
• 20 Design examples so learners can safely modify and rerun them.

• 1 Beginner: rewrite the example with different names and values.
• 2 Intermediate: add validation and handle one expected failure case.
• 3 Advanced: place Service Discovery in Microservices inside a small service-style design with tests.

• 1 Build a small Java console feature that demonstrates Service Discovery in Microservices.
• 2 Accept input, process it with the concept, print a clear result, and handle invalid input.
• 3 Add a README note explaining the design choice and two edge cases you tested.

• 1 If the program does not compile, check spelling, imports, braces, and file/class names first.
• 2 If output is unexpected, print intermediate values and verify each branch of the logic.
• 3 If the design feels complex, reduce it to the smallest working example and add pieces back one at a time.

• 1 Practice Service Discovery in Microservices with a second example from a business domain such as inventory, payroll, banking, or e-commerce.
• 2 Review related Java topics that cover data flow, error handling, testing, and clean design.
• 3 Compare your solution with official documentation and simplify anything you cannot explain clearly.