Skip to main content

Springboot - Eureka - registry

Eureka is a registry that helps with service registration and discovery. It is a central component of the microservices ecosystem, allowing service instances to register themselves and facilitating service discovery.

Eureka Server is a RESTful service that maintains a registry of all service instances. It provides a way for services to register themselves and for clients to discover the location of a service.

Eureka Client is a library that interacts with the Eureka Server to register, deregister, and discover other services.

Eureka is a key component of the Spring Cloud Netflix project, which provides a set of tools for building microservices.

Following are the benefits of using Eureka in Spring Boot:

  • Service Discovery: Eureka helps in discovering services in a distributed system.
  • High Availability: Eureka provides high availability by maintaining a registry of all service instances.
  • Load Balancing: Eureka can be used to implement load balancing between service instances.
  • Failure Detection: Eureka can detect failures of service instances and remove them from the registry.
  • Client Side Caching: Eureka clients can cache the registry information to improve performance.

Here are some of the challenges you might face while using Eureka:

  • Complexity: Eureka can be complex to set up and configure.
  • Performance: Eureka can have a performance impact on your system.
  • Security: Eureka needs to be properly secured to prevent unauthorized access.

Overall, Eureka is a powerful tool that can help you build and manage microservices. However, it is important to be aware of the challenges involved in using it. 






Comments

Post a Comment

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir...
Post a Comment
Read more

Lessons learned in Project Management

Lessons learned in Project Management Lessons learned (it may be +ve or -ve) in project management are the knowledge gained during a project that can be used to improve future performance. Lessons learned are documented with solutions to provide future project teams with information that can increase effectiveness and efficiency. Every project manager should be well aware of the impact lessons learned can have on the current and future projects. However, despite knowing the value of lessons learned, not everyone makes full use of them.  The lessons learnt documented using below process flow: 1) Identify: Identify comments and recommendations for use in future project. This is usually done through a project survey that is sent out to all team members. Various questions connected to a project help the participants share their lessons learned.  2) Document: Document and share the findings 3) Analyze: Analyze the finding and find the solution 4) Store: Store in a repository 5) Ret...
Post a Comment
Read more