1
头图

Our "Cloud Native Application Journey-Kubernetes Growth" series of articles have been updated again!
This is the fifth article in this series. Since the content of this series of articles is progressive, if you have not read the previous content, please review it through the following links to establish the necessary foundation, and then join us on the journey of cloud native applications.

  1. know Kubernetes
  2. Understanding Kubernetes
  3. know Azure Kubernetes Service
  4. Explore and practice Kubernetes

In this issue, we will lead everyone to discuss the content related to microservices. In particular, we will discuss some precautions for running the microservice architecture on Azure Kubernetes and DevOps.

Day 21-25: Introducing microservice architecture

Microservices usually refer to an architecture platform that supports continuous development, system scalability, application decoupling, and multi-language programming. It creates a more flexible and more adaptable IT infrastructure, and each service is independent of each other, so that advanced functions can be added more efficiently without changing the infrastructure.
As the carrier of microservice operation, container directly promotes the development of microservice and solves the problem of microservice deployment and isolation. However, a large application usually consists of a large number of microservices and containers. At this time, the management, monitoring and scheduling of the container cluster will pose certain challenges. The emergence of Kubernetes has solved this problem well. It has a rich scheduling strategy and built-in container monitoring and management functions.
After the microservice architecture is adopted, due to the diversity of business models and technical components, multiple microservice deployable units will be generated after the application is split, which brings some challenges to the technical team, such as the number of builds and deployment examples Too much, the trouble of manual management, too many running instances, and it is difficult to locate faults, etc., which must be completed by DevOps.
Therefore, at this stage, we will prepare some learning materials for you to help you understand the infrastructure and DevOps considerations of running microservice architecture on Azure Kubernetes, including the basic Azure Kubernetes settings, so as to help you understand how to deploy microservices. service.

Click here to start the journey

After the content of this stage is completed, I believe you will gain a deeper understanding of the idea of running microservice architecture and infrastructure on Azure Kubernetes. In the next journey, we will lead everyone to experience the charm of Azure Kubernetes at close range through practice. Stay tuned for more exciting content!
In addition, do you have any thoughts or suggestions regarding the content of this article and the follow-up arrangements for this series of articles? Also welcomes the publication of your thoughts by commenting message, we will pick a wonderful message and send fine gifts one. Everyone is welcome to participate actively, and also welcome to share this article with more friends who are interested in cloud-native development, we will learn together and make progress together!


微软技术栈
423 声望998 粉丝

微软技术生态官方平台。予力众生,成就不凡!微软致力于用技术改变世界,助力企业实现数字化转型。