Learn to use client side load balancing using spring cloud ribbon with eureka. Learn to build microservice which use ribbon as client side load balancer.
Spring boot is widely being used while delivering micro services based application. Eventually it has become a necessity to monitor Spring boot applications running on different hosts. There are many tools available to monitor different health stats of these microservices. In this post, we will learn to use three such monitoring tools i.e. Hystrix dashboard, […]
Zipkin is very efficient tool for distributed tracing in microservices ecosystem. Distributed tracing, in general, is latency measurement of each component in a distributed transaction where multiple microservices are invoked to serve a single business usecase. Let’s say from our application, we have to call 4 different services/components for a transaction. Here with distributed tracing […]
Netflix zuul example using zuul API gateway pattern. Learn to create load balancer using Netflix Zuul and its solid bonding with Spring Cloud.
Learn to create Microservices, based on Spring cloud, registering on HashiCorp Consul registry server and how other microservices (discovery clients) use it to register and discover services to call their APIs.
Learn to leverage the one of the Spring cloud Netflix stack component called Hystrix to implement circuit breaker while invoking underlying microservice. It is generally required to enable fault tolerance in the application where some underlying service is down/throwing error permanently, we need to fall back to different path of program execution automatically. This is […]
Learn to deploy and host spring boot applications into Pivotal Cloud Foundry Web Services Platform (PWS) and access REST endpoint from local workstation.
Learn to create microservice, based on Spring cloud, which act as Netflix Eureka registry server and how other microservices (Eureka clients) use it to register and discover services.
Config server is where all configurable parameters of microservices are written are maintained. It is more like externalizing properties / resource file out of project codebase to an external service altogether, so that any changes to that property does not necessitate the deployment of service which is using the property. All such property changes will be reflected without redeploying the microservice.