Skip to main content

How to communicate two microservices with different ports?

 When two microservices need to communicate with each other but are running on different ports, there are a few approaches :

  1. 1.Direct Communication: If the microservices are deployed on the same network or infrastructure, they can communicate directly using their network addresses. You can use HTTP or any other appropriate protocol for communication. In this approach, each microservice would need to know the network address (IP address or domain name) and the port of the other microservice.

  2. Example:

  3. Microservice A running on port 8080 wants to communicate with Microservice B running on port 9090. Microservice A can make an HTTP request to Microservice B using its network address and port:

  4. HttpClient client = HttpClient.newHttpClient(); HttpRequest request = HttpRequest.newBuilder() .uri(URI.create("http://localhost:9090/api/resource")) .build(); HttpResponse<String> response = client.send(request, HttpResponse.BodyHandlers.ofString());


  5. 2.Service Discovery: Service discovery is a mechanism that allows microservices to locate and communicate with each other dynamically. Instead of hardcoding network addresses, you can utilize a service registry (e.g., Consul, Eureka, or ZooKeeper) that keeps track of available services and their network locations. Microservices can register themselves with the service registry upon startup and discover other services when needed. The service registry acts as a central point for service discovery, enabling communication between microservices regardless of their ports.

  6. Example : Microservice A and Microservice B register themselves with a service registry (e.g., Consul). When Microservice A needs to communicate with Microservice B, it queries the service registry to discover the network address and port of Microservice B dynamically:

// Pseudo code for service discovery using Consul
String serviceUrl = consulClient.lookupServiceUrl("microservice-b");
// Use serviceUrl for communication

  1. 3.API Gateway: An API gateway acts as an entry point for clients and can also help in communication between microservices. You can configure the API gateway to route requests to the appropriate microservice based on the request path or other criteria. This way, the microservices can run on different ports, but clients communicate with a single endpoint provided by the API gateway. The API gateway handles the routing and forwarding of requests to the appropriate microservice.

  2. Example:

  3. Microservice A and Microservice B run on different ports, but they are exposed through an API gateway running on port 8080. Clients make requests to the API gateway, which routes the requests to the appropriate microservice:

  4. // Request from the client to the API gateway (running on port 8080) GET http://localhost:8080/microservice-a/api/resource

The API gateway handles the request and forwards it to Microservice A running on a different port.

  1. 4.Message Queue/Message Broker: Another approach is to use a message queue or message broker system like Apache Kafka or RabbitMQ. Microservices can communicate by publishing messages to a specific topic or queue, and the receiving microservice can consume those messages from the queue. The message broker acts as an intermediary, decoupling the communication between microservices. Each microservice would need to connect to the message broker using its own port, and the broker takes care of routing messages between them.

  2. Example :

  3. Microservice A and Microservice B communicate through a message broker (e.g., Apache Kafka). Microservice A produces a message to a specific topic, and Microservice B consumes messages from that topic:


  4. // Microservice A (producer) kafkaProducer.send(new ProducerRecord<>("my-topic", "message")); // Microservice B (consumer) ConsumerRecords<String, String> records = kafkaConsumer.poll(Duration.ofMillis(100)); for (ConsumerRecord<String, String> record : records) { // Process the received message }


The choice of approach depends on factors such as the complexity of your microservices architecture, scalability requirements, and specific use cases. Consider the characteristics of your system and select the most suitable approach for your scenario.

Comments

Popular posts from this blog

JDK 25: The new features in Java 25

 Java Development Kit (JDK) 25, scheduled for release in September 2025, is set to introduce several significant enhancements. Here's an overview of the notable features: 1. Stable Values API (Preview): This feature introduces stable values—objects holding immutable data treated as constants by the Java Virtual Machine (JVM). By allowing greater flexibility in initialization timing compared to final fields, stable values aim to improve application startup times. They enable performance optimizations akin to constant-folding, previously exclusive to JDK code, and ensure thread-safe, single-time initialization. This decouples the creation of stable values from their initialization without significant performance penalties.  2. Removal of 32-bit x86 Port: JDK 25 plans to eliminate both the source code and build support for the 32-bit x86 port, which was deprecated in JDK 24. Maintaining this port has become less beneficial, especially with the challenges in keeping it updated wit...

what is circuit breaker in microservice

   A circuit breaker is a design pattern used in microservice architecture to improve the resilience and fault tolerance of the system. In a microservice architecture, multiple services work together to deliver a business function. When a service is not available, the downstream services depending on it may start to fail as well, leading to a cascading failure. A circuit breaker helps prevent cascading failures by monitoring the status of the dependent services. If a dependent service is not responding, the circuit breaker trips and redirects the traffic to a fallback mechanism, such as a cache or a default response. The circuit breaker periodically attempts to reconnect to the dependent service, and once it's available, it resumes directing traffic to it. The circuit breaker pattern helps prevent failures from spreading across the system, improves the availability of the overall system, and can help reduce the load on dependent services.

Java RoadMap