This is indeed the best article on microservice architecture I have read!

In 2014, Martin Fowler and James Lewis jointly proposed the concept of microservices, which defined microservices as small services composed of a single application, with their own itineraries and lightweight processing, services designed according to business functions,Deploy in a fully automated fashion, using HTTP APIs to communicate with other services.At the same time, the service will use the smallest scale centralized management (such as Docker) capabilities, and the service can be implemented with components such as different programming languages ​​and databases.

Microservicesare small, autonomous services that work together.

Microservices andSOA

Service-Oriented ArchitectureSOA(Service-Oriented Architecture) sounds similar to microservices, but SOA used earlyBus mode, this bus mode is strongly bound to a certain technology stack, such as: J2EE.This makes it difficult for the legacy systems of many enterprises to be connected, the switching time is too long, the cost is too high, and the convergence of the stability of the new system takes some time. In the end, SOA looks beautiful, but it has become an enterprise-level luxury.Intimidating.

Microservice Architecture

In view of the above-mentioned shortcomings of "monolithic application", a single application is divided into various small, interconnected microservices, and a microservice completes a relatively single function, and each otherKeep it separate and decoupled, that's the microservice architecture.

Technological heterogeneity

The internal development technology of different services can be inconsistent. You can use java to develop helloworld service A and golang to develop helloworld service B, and everyone no longer has to argue about which language is the best language in the world.

Scalability

If there is a performance bottleneck in a huge single service, it can only expand the software as a whole. It may only affect the performance of a small module, and we have to pay the price of upgrading the entire application.This has been improved in the microservice architecture. You can only expand and upgrade those services that affect performance, so the effect of the right medicine is very good.

Simplified deployment

If your service is a huge monolith with millions of lines of code, it is obviously very cumbersome to recompile the entire application even if a few lines of code are modified, and the uncertainty brought about by software changesThe reliability is very high, and the impact of software deployment is also very large.In the microservice architecture, the deployment of each service is independent. If there is a problem, it only affects a single service, and the version can be quickly rolled back to solve it.

Service registration and discovery

Microservices call each other to complete the overall business function. How to find the correct target service address among many microservices is the so-called "service discovery" function.

No technology is forever in the IT world, the evolution of microservices architecture is one example.We don't know when the next technology iteration will be, but the microservice framework has never stopped updating every second of every day we work hard.As a corner of the IT industry, we should be enthusiastic about technology, actively face change, and use new technology to make us stand at the top again.