Spring Cloud Netflix Eureka

 In the phone section, you will learn what Eureka Discovery Service is, how to create and how to start

up your own discoveries.

Harris.

When working with Eureka Discovery Service, reading is the commendation or when discussing it with

your team members, you might hear that it is also referred to as sprinklered, Netflix's Eureka.

And this is because Eureka Discovery Service is actually a project that Netflix has built for their

own needs and until now is actively using it.

And I'm sure you have heard of Netflix.

The are a very popular movies streaming service.

And today lots of people in the world use Netflix to watch movies at home.

So Netflix has built Eureka for their own needs.

And later, Eureka project became part of sprinklered.

And it is now being used not only by Netflix, but also by thousands of other developers around the

world.

So what is Eureka?

Do Eureka helps MICRA services find each other?

Let's say we have a client application, like, for example, a mobile application, and let's say we

have a microspheres and it's called products microspheres.

So if a klong application wants to communicate with our products microspheres, it needs to know its

address.

And the other is usually looks like a domain name or an IP address and then the portal number.

So for a client application to be able to send requests to products, microspheres, it needs to know

the address so that it can send a request to it.

So what we can do here is we can hard code the address of products, microspheres in our client application,

and then our mobile application will be able to communicate with products.

Macassar is just fine, but what if we need to scale this up and start more instances of products microspheres?

Please note that each additional instance of products microspheres will need to start up on its own

porth number, which means a different address or a mobile application does not know this new Newport

numbers and it will not be able to send the request to this new instances of products microspheres.

It will continue to communicate with only one hundreds of products.

My concern is that it is aware of which is Porth number 88 and here comes Eureka Discovery Seris.

When each instance of products Makassar a start up, it will register itself with Eureka Discovery,

Seris.

So Eureka will know the address of each microspheres.

And if there are three instances of products microspheres, Eureka will know the address of each of

them.

One new instance of products microspheres starts up.

It will register with Eureka itself.

You do not need to open Eureka configuration file and manually add the location of your microspheres

type.

So if a load on your application increases and you need to start up ten more instances of products microspheres,

then you can easily do that.

And each new microspheres will have registered with Eureka itself and Eureka will know where it is located.

It will know which IP address and which porth number to use.

Similarly, when you do not need so many instances of products microsurgeons, you can stop some of

them.

And when you stop, they are not needed.

Micro Ceressus their location will be removed from Eureka.

Mathematically, you do not need to update configuration files manually.

So this helps you to quickly scale up your application up and down as needed without manually configuring

and removing the location of each micro series from Eureka Discovery.

Then we add into our architecture API Gateway and a load balancer Eureka Service will tell our API gateway

about the location of each instance of products microspheres.

Our client application will then need to communicate with products.

Manorexia is via API Gateway.

It will send the ship request to products microsurgeons.

And since API Gateway now knows that there are more than one instance of products microsurgery training.

And this is thanks to Eureka, the load balancer client of our banquet, we will then balance the load

and want these micro Ceressus as needed.

And I'll show you how to configure Eureka and how to configure your MICRA services to work together.

And I'll also show you how to make it work together with API Gateway as we move on.

All right.

So let's continue.

Chapter 2 Setting Up Eureka in Application

In this video, we're going to create and run our very own Eureka Discovery server, and I have Spinto

suite running.

I have an empty workspace created.

And to create a new Eureka Discovery server, I'll need to create a new Springwood project.

So I'll go to file and then new and choose a spring starter project.

Here, I'll provide project details, I'm going to be creating an API for my forum, so I'll give my

Eureka Discovery server a name for the app and then discover a service like this.

I will then provide group ID, which is going to be my package name.

Com Developer block for the discovery and then artifact, which is going to be my project name for the

Discovery Service version.

I will leave as is description.

I will also change.

I will type photo up Eureka Discovery server and the package is AMS developer block for the discovery.

All right.

So I'll click on next.

And here I'll need to provide dependancy.

And for this project, the basic dependencies are Eureka.

So I will start typing Eureka and will filter the list of available dependency by this keyword.

And there are two dependencies that I want to select, Eureka Discovery and Eureka Server.

OK, now click next and then click on Finish.

This will create a new Springwood project for me and I can expand it and have a look at pomoc example

that was created for me.

Here I have my project details.

This is group ID, artifact ID, project name description, the sprinklered version, which is being

used green, which release, and then the two dependencies that we have added.

This is cloud starter, Netflix, Eureka Client and Sprinklered, starter starter, Netflix, Eureka

Server.

Now, this might be a little bit confusing that this print good application is both Eurekas, Silver

and Eureka Client Month.

And this is fine.

Eureka Discovery Service can act as a client, but we will further configure this project to make it

act as a server only and we will disable some of the common features and we have dependency management

section, plug ins and repositories.

OK, so now when we are ready with our maximum, I'll say it and I will go to Maine and then my main

package and here I have my application for Discovery, serious application.

So to make this spring springboard application to work as a Eureka Discovery server, I'll need to add

one more notation here.

And this annotation is called Aníbal Eureka Server.

Like this, let me import this annotation import enable Eureka server from Orrock Spring Framework Cloud

Netflix, Eureka Server.

All right.

And the next step for us is to provide some configuration properties.

I'll go to source my resources and open application properties and I will paste a few lines and I will

work here.

From the very first line is the server port with specific port number on which this spring board application

will start and run.

Then we specify the spring application name.

This is the name by which this particular application will be known.

And then because Eureka server can be at the same time a client application, we need to specify this

two lines Eureka client register with Eureka and set it to false to prevent this application to register

with Eureka as a client and to disable the feature registry.

All right.

And the next line is the service euro default zone.

This is the fully qualified euro by which client applications communicate with Eureka server.

I will save this application properties file now and I can run this application and see how you vehicle

dashboard looks like.

So I'll select my project and the right mouse click run us and then choose a spring put up.

I'll have to wait a little for this application to start up, OK?

It started on board eight to 10 and I can bring up my browser window and then go to localhost port number

eight 10 and hit enter.

And this will bring up the Eureka dashboard and has some useful information like system information.

You can have a look and then the replicas and then instances that are currently registered with Eureka.

We don't have any applications registered, but as we create and start up our new micro services, they

will register and will appear in the list of applications here.

Then we have some general information and then instant information like IP address and whether it's

up and running.

All right.

So this is the dashboard which will be coming here from time to time to look at the registered instances.

They will appear in this list.

But for now, we know that Eureka server is running and we're good to continue.