In the past few years, the term “microservices architecture” has emerged to describe a specific way of designing software applications as a suite of independently deployable services.
49 PPT dry goods: origin, introduction and design of microservices architecture
Although there is no precise definition of this architectural style, there are some common characteristics around business capabilities, automated deployment, endpoint intelligence, and decentralized control of language and data.
“Microservices” is another new term on the crowded software architecture street. Despite our natural tendency to pass such things off with disdain, these terms describe a style of software systems that we find increasingly appealing.
We’ve seen many projects adopt this style over the years, and the results so far have been positive, so it’s becoming the default style for many of us to build enterprise applications. Sadly, there isn’t much information outlining the style of microservices and how to do it.
In short, microservices architecture is a way of developing a single application as a set of small services, each running in its own process and communicating with a lightweight mechanism (usually an API for HTTP resources).
These services are built around business functions and can be deployed independently through a fully automated deployment mechanism. Centralized management of these services is minimal, and they can be written in different programming languages and use different data storage technologies.
Let’s take a closer look at the origins, introduction and design of microservices architecture through 397 PDF pages.
Like + follow, private message to get all the information, the blogger wechat: YDT676, welcome harassment
