learn microservices

Consul is a service registration discovery tool launched by HashiCorp, written in Golang and open source. Consul is naturally cross-platform and easy to deploy. It has a web management background for users to view and maintain the Consul cluster. In addition to the service registration discovery function, Consul also supports Key/Value storage, which can be used as a simple configuration center. Consul's architecture supports multi-data center deployment, and each data center has multiple Consul nodes. Consul's nodes were divided into Server mode and Client mode. The Server mode nodes were cluster nodes in the true sense, and the CARs in the CAP were implemented through the RAFT algorithm. Consul also provided a health check function and a web management page. Overall, Consul was a powerful and simple microservice registrar.

The main microservice registration centers were Eureka, Consul, ZooKeeper, and Nacos.

The microservice registration center is a basic component of the microservice architecture. It is used for automatic discovery and dynamic route of services. It can receive registration requests for microservice instances and store the instance information in the registration table. Through the registration center, service consumers can find and call the services they need according to the service name or other identification. The registration center can also achieve Load Balancer and fail over to ensure high service utilization. A microservice gateway is a component used in a separate or independent application in a microservice architecture. Its main function was to uniformly register and access the internal microservice component modules 'API interface capabilities to the gateway, and provide a unified interface service to the outside world. Through the gateway, the client only needs to access the exposed interface of the gateway, and there is no need to directly call the interface of each microservice. The gateway could also achieve security isolation, permission verification, monitoring, Load Balancer, and other functions to provide a better user experience and system performance. In the microservice architecture, the registrar and gateway were two independent components, each with different functions and application scenarios. The registration center was mainly used for automatic discovery and route of services, while the gateway was used for unified management and exposure of interface services. They play an important role in the microservice architecture, improving the system's flexibility, flexibility, and reliability. (Source: Doc3, Doc4, Doc7)

Eureka is a microservice registration center for communication between microservices. It consists of the Eureka server and the Eureka client. The Eureka server was responsible for the registration and discovery of services, while the Eureka client was responsible for interacting with service suppliers and service consumers. When a microservice starts, it will register its service information with the Eureka server and send a heartbeat regularly to keep the contract renewed. If the Eureka server does not receive a heartbeat within a certain period of time, the service will be removed from the service list. When a service consumer needs to call a service supplier, it will obtain the service supplier's address from the Eureka server and store the address in the local buffer so that it can be directly retrieved from the local buffer the next time it is called. Eureka was easy to use, stable, and reliable, so it was widely welcomed. It is a component of the Spring Cloud framework that implements service registration and discovery functions.

One horror story could be when the communication between microservices breaks down. For example, if there is a misconfiguration in the API calls. Suddenly, data stops flowing properly between services and the whole application starts to malfunction. The end - user experience becomes terrible as parts of the app stop working.

Well, start by clearly defining the user and their goal. Then describe the actions they'll take and the expected outcome. Keep it simple and focused.

To write good user stories for microservices, you need to understand the microservice's functionality and the user's context. Focus on the value the user gets from the service and break it down into manageable chunks. Also, make sure the stories are testable and have acceptance criteria.

Sure. There was a case where a microservice handling data storage was not properly configured for backup. Due to a hardware failure in the server, all the data it was responsible for was lost. Since the microservice was isolated, the other parts of the application couldn't access the data either, causing major disruptions in the business operations.

I recommend the book "The Sweet Wife Is Unattainable". One of the main characters is the business tycoon Lan Fuchu, the male lead. The female lead, Su Yi, was a strong woman with the identity of a secret agent. Their relationship was not smooth, but they eventually came together and formed a 1v1 love story. I hope you like this fairy's recommendation. Muah ~😗

I recommend " Fragrance Control ". This book was written by the author, Qing Liu. It's a fantasy romance-Oriental fantasy novel. The general plot of this novel was about the Qing Emperor. It was said that wherever he went, the grass was fragrant and the flowers were in full bloom. With a wave of his hand, the dead trees would revive, and the flesh and bones would die. At the same time, the sentences in this book are beautiful and very suitable for your requirements. I hope you like my recommendation.😗