Explore topic-wise InterviewSolutions in .

Eureka is the NETFLIX Service DISCOVERY Server and CLIENT. Eureka Server is using Spring Cloud.

Eureka is the Netflix Service Discovery Server and Client. Eureka Server is using Spring Cloud.

Server side load balancing can be achieved using Netflix Zuul. Zuul is a JVM based router and server side load balancing by Netflix. It provides a single entry to our system, which allows a browser, MOBILE app, or other user interface to consume services from multiple hosts WITHOUT managing cross-origin resource SHARING (CORS) and authentication for each one. We can integrate Zuul with other Netflix projects like Hystrix for fault tolerance and Eureka for service discovery, or use it to manage ROUTING rules, filters, and load balancing across your system.

Server side load balancing can be achieved using Netflix Zuul. Zuul is a JVM based router and server side load balancing by Netflix. It provides a single entry to our system, which allows a browser, mobile app, or other user interface to consume services from multiple hosts without managing cross-origin resource sharing (CORS) and authentication for each one. We can integrate Zuul with other Netflix projects like Hystrix for fault tolerance and Eureka for service discovery, or use it to manage routing rules, filters, and load balancing across your system.

1. LOAD Balanced RestTemplate.
2. If there are MULTIPLE RestTemplate you get the RIGHT one.
3. It can used to ACCESS multiple microservices.

SPRING Cloud support SEVERAL ways to implement service discovery but for this I am GOING to use Eureka CREATED by Netflix. Spring Cloud provide several annotation to make it use EASY and hiding lots of complexity.

Spring Cloud support several ways to implement service discovery but for this I am going to use Eureka created by Netflix. Spring Cloud provide several annotation to make it use easy and hiding lots of complexity.

When we START a project, we usually have all the configurations in the properties file. As more and more services are developed and deployed, adding and modifying these properties become more complex. Some services might go down, while some the location might change. This MANUAL CHANGING of properties may create issues. EUREKA Service Registration and Discovery helps in such scenarios. As all services are registered to the Eureka server and lookup DONE by calling the Eureka Server, any change in service locations need not be handled and is taken care of.

When we start a project, we usually have all the configurations in the properties file. As more and more services are developed and deployed, adding and modifying these properties become more complex. Some services might go down, while some the location might change. This manual changing of properties may create issues. Eureka Service Registration and Discovery helps in such scenarios. As all services are registered to the Eureka server and lookup done by calling the Eureka Server, any change in service locations need not be handled and is taken care of.

Spring Boot provides actuator endpoints to monitor metrics of individual microservices. These endpoints are very helpful for getting information about applications like if they are up, if their components like database etc are WORKING good. But a major drawback or difficulty about using actuator enpoints is that we have to individually hit the enpoints for applications to KNOW their status or health. Imagine microservices involving 50 applications, the admin will have to hit the actuator endpoints of all 50 applications. To help us DEAL with this situation, we will be using open source project located at Built on TOP of Spring Boot Actuator, it provides a web UI to enable us visualize the metrics of multiple applications.

Spring Boot provides actuator endpoints to monitor metrics of individual microservices. These endpoints are very helpful for getting information about applications like if they are up, if their components like database etc are working good. But a major drawback or difficulty about using actuator enpoints is that we have to individually hit the enpoints for applications to know their status or health. Imagine microservices involving 50 applications, the admin will have to hit the actuator endpoints of all 50 applications. To help us deal with this situation, we will be using open source project located at Built on top of Spring Boot Actuator, it provides a web UI to enable us visualize the metrics of multiple applications.

Eureka CREATED by Netflix, it is the Netflix Service DISCOVERY Server and Client. Netflix Ribbon, it PROVIDE SEVERAL algorithm for Client-Side LOAD Balancing. Spring provide smart RestTemplate for service discovery and load balancing by using @LoadBalanced annotation with RestTemplate instance.

Eureka created by Netflix, it is the Netflix Service Discovery Server and Client. Netflix Ribbon, it provide several algorithm for Client-Side Load Balancing. Spring provide smart RestTemplate for service discovery and load balancing by using @LoadBalanced annotation with RestTemplate instance.

Microservices Advantages

• Smaller code base is easy to maintain.
• Easy to scale as individual component.
• Technology diversity i.e. we can mix libraries, databases, frameworks etc.
• Fault isolation i.e. a process failure should not BRING whole system down.
• Better support for smaller and PARALLEL team.
• Independent deployment
• Deployment time reduce

Microservices Disadvantages

• Difficult to achieve strong consistency across services
• ACID transactions do not span multiple processes.
• Distributed System so hard to debug and trace the issues
• Greater need for end to end TESTING
• Required cultural changes in across teams like Dev and Ops working TOGETHER even in same team.

Microservices Advantages

Microservices Disadvantages

Microservices ARCHITECTURE allows to avoid monolith application for large system. It PROVIDE LOOSE coupling between COLLABORATING processes which running independently in different environments with tight cohesion.

Microservices architecture allows to avoid monolith application for large system. It provide loose coupling between collaborating processes which running independently in different environments with tight cohesion.

When developing distributed microservices with Spring Boot we face the following issues-

• Complexity associated with distributed systems-
  This overhead includes network issues, Latency overhead, Bandwidth issues, security issues.
• Service Discovery-
  Service discovery tools manage how processes and SERVICES in a cluster can find and talk to one another. It involves a directory of services, REGISTERING services in that directory, and then being able to lookup and connect to services in that directory.
• Redundancy-
  Redundancy issues in distributed systems.
• Loadbalancing-
  Load balancing improves the distribution of WORKLOADS across multiple computing resources, such as computers, a computer cluster, network LINKS, central processing units, or disk drives.
• Performance issues-
  Performance issues DUE to various operational overheads.
• Deployment complexities-
  Requirement of Devops skills.

When developing distributed microservices with Spring Boot we face the following issues-

Spring Cloud Stream APP Starters are Spring Boot based Spring Integration applications that provide integration with external SYSTEMS. Spring Cloud Task. A short-lived microservices framework to QUICKLY BUILD applications that perform FINITE amounts of data processing.

Spring Cloud Stream App Starters are Spring Boot based Spring Integration applications that provide integration with external systems. Spring Cloud Task. A short-lived microservices framework to quickly build applications that perform finite amounts of data processing.

Microservices is a variant of the SERVICE-oriented architecture (SOA) ARCHITECTURAL style that structures an application as a collection of loosely coupled services. In a microservices architecture, services should be fine-grained and the PROTOCOLS should be lightweight. The benefit of decomposing an application into different smaller services is that it improves modularity and makes the application easier to UNDERSTAND, develop and test. It also parallelism development by enabling small autonomous teams to develop, deploy and scale their respective services independently. It also allows the architecture of an individual service to emerge through continuous refactoring. Microservices-based ARCHITECTURES enable continuous delivery and deployment.

Microservices is a variant of the service-oriented architecture (SOA) architectural style that structures an application as a collection of loosely coupled services. In a microservices architecture, services should be fine-grained and the protocols should be lightweight. The benefit of decomposing an application into different smaller services is that it improves modularity and makes the application easier to understand, develop and test. It also parallelism development by enabling small autonomous teams to develop, deploy and scale their respective services independently. It also allows the architecture of an individual service to emerge through continuous refactoring. Microservices-based architectures enable continuous delivery and deployment.