Why Need of Naming Server

 Suppose if we are using Ribbon than it needs a configured if any new server comes up 

suppose currently only 2 server was there 8001 and 8000  as given below application .properties file only configured with two server now for any new server like 8002 comes up as we didnt configured into the application properties file

currency-exchange-service.ribbon.listOfServers=http://localhost:8000,http://localhost:8001

So for dynamicaly increase and decreasing we need naming server(EurekaNamingServer)

All the instances of All Microservices would register with naming server, that is called service Registration


whenever service want to talk to another service like CurrencyCalculationService wants to talk to the CurrencyExchangeService, what would do, it would talk to the NameServer, and it would ask the NameServer what are the instances of the currencyExchangeService that are currently running? This is called Service Discovery

  1. Service Registration: All Microservice Register with Eureka naming server
  2. Service Discovery: Asking to the Eureka Naming server and ask How many Service running for specific service is known as service Discovery
Given Above dependancies is requried for Naming server project to be Create

Step 1:  for resolving Bootstrape Error Add Givne Below Dependancies
<dependency>
    <groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-bootstrap</artifactId>
</dependency>

Step 2: Add Given properties in application.properties file

spring.application.name=netflix-eureka-naming-server

server.port=8761


Step 3: add @EnableEurekaServer in main class for Enabling Eureka Server

@SpringBootApplication

@EnableEurekaServer

public class NetflixEurekaNamingServerApplication {


public static void main(String[] args) {

SpringApplication.run(NetflixEurekaNamingServerApplication.class, args);

}


}



Step 4: by hitting http://localhost:8761/ you can see the eureka server UI which shows Eureka Server up and running




Lets Us Given Below Pom.xml file

<?xml version="1.0" encoding="UTF-8"?>

<project xmlns="http://maven.apache.org/POM/4.0.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>

<parent>

<groupId>org.springframework.boot</groupId>

<artifactId>spring-boot-starter-parent</artifactId>

<version>2.1.9.RELEASE</version>

<relativePath /> <!-- lookup parent from repository -->

</parent>

<groupId>com.khan.microserservices</groupId>

<artifactId>netflix-eureka-naming-server</artifactId>

<version>0.0.1-SNAPSHOT</version>

<name>netflix-eureka-naming-server</name>

<description>netflix eureka naming server</description>

<properties>

<java.version>1.8</java.version>

<spring-cloud.version>Greenwich.SR3</spring-cloud.version>

</properties>

<dependencies>

<dependency>

<groupId>org.springframework.boot</groupId>

<artifactId>spring-boot-starter-actuator</artifactId>

</dependency>

<dependency>

<groupId>org.springframework.cloud</groupId>

<artifactId>spring-cloud-starter-config</artifactId>

</dependency>

<dependency>

<groupId>org.springframework.cloud</groupId>

<artifactId>spring-cloud-starter-netflix-eureka-server</artifactId>

</dependency>


<dependency>

<groupId>org.springframework.boot</groupId>

<artifactId>spring-boot-devtools</artifactId>

<scope>runtime</scope>

<optional>true</optional>

</dependency>

<dependency>

<groupId>org.springframework.boot</groupId>

<artifactId>spring-boot-starter-test</artifactId>

<scope>test</scope>

</dependency>

<!-- <dependency>

<groupId>org.springframework.cloud</groupId>

<artifactId>spring-cloud-starter-bootstrap</artifactId>

</dependency>-->

</dependencies>

<dependencyManagement>

<dependencies>

<dependency>

<groupId>org.springframework.cloud</groupId>

<artifactId>spring-cloud-dependencies</artifactId>

<version>${spring-cloud.version}</version>

<type>pom</type>

<scope>import</scope>

</dependency>

</dependencies>

</dependencyManagement>


<build>

<plugins>

<plugin>

<groupId>org.springframework.boot</groupId>

<artifactId>spring-boot-maven-plugin</artifactId>

<configuration>

<image>

<builder>paketobuildpacks/builder-jammy-base:latest</builder>

</image>

</configuration>

</plugin>

</plugins>

</build>


</project>


Comments

Post a Comment

Popular posts from this blog

Microservice with Java Spring Cloud

Image
 Definations of Microservice: By Sam NewMan: - Small autonomous services that work together By James :- Style is an approach to developing a single application as a suit of small services, each running in its own process and commuinicating with lightweight mechanism, often an HTTP resourece API , These services are build around business capabilities and independently deployable by fully automated deployment machinery, there is a bare minimum of centralized management of these services, which may be ritten in different programming languagees and use different data storage technologies  MICROSERVICES REST and Small well chosen deployable units and Cloud Enable CHALANGEST WITH MICROSERVICE 1.  Bounded Context How to decided boundris of microservices id difficul 2.  Configuration Management Suppose we have 5 or 50 microservices, thse microservices have multiple instances in each environment and there are multiple environments Let say we have 10 microservices, with 5 env...
Read more

STEP 10 Configure Porfile for Limit service

Image
 Now by adding into bootrap.properties  the profile which you want to be in your Limit-Service spring.profiles.active= qa we are getting 2 as minimum but 888 is coming from default as maximum did not set into the limit-service-qa.properties this is default file it will pick up the value from the QA which is resited in the limits-service-qa.properties file spring.profiles.active= dev Similartly it will pick up the value from the DEV which is resited in the limits-service-dev.properties file 1. this is one of the way to pass in the active profile  2. And also add VM arguments spring.profiles.active-dev  3. Java command line arguments
Read more

STEP 9 Connect Limit service to Spring Cloud Config Server

Image
  Till now we have Connected the Spring cloud config server to GIT repository also configured with multiple environment as well But still we have not configured Limit service with spring cloud config server  In this Tutorial we will Connect LimitService to pick up the configuration from the spring cloud config server As of now all the properties are seted for limit service are present in application.properties STEP 1: Change application.properties to bootstrap.properties in Limit-service  STEP 2:   instead of using local service add the path of your spring-cloud-config-server spring.application.name= limits-service spring.cloud.config.uri= http://localhost:8888 Here is two Properties  1. spring.application.name this should be similar name of yoru spring-cloud-config-server file folder  2.  spring.cloud.config.uri this will contain the port information where our spring-cloud-config-server deployed Now able to achive the property of spring-cloud-...
Read more