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

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more

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

4 T's - Technology, Time, Teamwork, Transparency

 1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished.  3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...
Post a Comment
Read more