Shulou(Shulou.com)06/02 Report--

This article will explain in detail the sample analysis of Docker and micro-services. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

A brief History of SOA

In early 2000, we witnessed the rise of Service-oriented Architecture (Service Oriented Architecture,SOA), a very popular software architecture design paradigm. In short, SOA is a software architecture pattern for building large enterprise applications that usually require the integration of multiple services, each of which is built using a different platform and programming language and interacts through a common communication mechanism.

The following is a simple illustration of service-oriented architecture (SOA):

Cymbals

Key points

SOA is the first choice for large software products, such as enterprise applications.

SOA focuses on integrating multiple services into a single application, rather than emphasizing modular applications.

In SOA, the common communication mechanism for interaction between services is called Enterprise Service bus (Enterprise Service Bus,ESB).

SOA-based applications are monolithic in nature. That is, a single application layer contains a user interface or presentation layer, a business logic or application layer, and a database layer, all of which are integrated into one platform.

About "single Architecture"

Let's take the online store as an example. We know that many e-commerce websites can be accessed through a variety of devices, so these sites usually provide different user interfaces for laptops and mobile devices.

We also know that multiple operations or services depend on each other to ensure the proper operation of the application. Some of these services are responsible for creating accounts, displaying product catalogs, creating and verifying shopping carts, generating bills, confirming orders, completing payments, and so on.

In a single application, all of these services run on the same application layer, so the software architecture of this e-commerce site is as follows:

Shortcoming

It is clear that as the number of services increases, the size of the application will continue to grow. This can overwhelm developers who build and maintain the application code base.

It is difficult to update the current technology stack, and even changing a little bit in the current technology stack can be a nightmare.

Each change requires the developer to rebuild the entire application, which is a waste of resources.

As our customer base increases, we will have more requests, which will require more resources. Therefore, it is critical to build scalable products. For single applications, we can only scale in one direction, that is, vertically, not horizontally. This means that we can scale applications on a single computer by adding more hardware resources such as memory and CPU, but scale-out (across multiple computers) remains a challenge.

Here I would like to recommend a Java advanced group: 725633148 will share some videos recorded by senior architects: (there are Spring,MyBatis,Netty source code analysis, principles of high concurrency, high performance, distributed, micro-service architecture, JVM performance optimization, distributed architecture), etc., which have become essential knowledge systems for architects to get free of charge.

Here comes the savior "micro service"!

Micro-service architecture can be regarded as a specialization of SOA and an alternative model that can overcome the shortcomings of single architecture.

In the micro-services architecture, we focus on modularizing the application and breaking it down into smaller, independent services that can be built, deployed, scaled, and maintained independently of other services or the entire application itself. These independent services are called micro-services, so this architecture is called micro-service architecture.

Phellodendron mandshurica (Thunb.)

Key points

Microservices architecture and SOA are different, but they do have some similarities. The microservice architecture is called a variant of SOA, or even a specialization of SOA. In other words, SOA can be thought of as a superset of microservice architectures.

People can find similarities between these architectures mainly because they are focused on building services with loose coupling. These services have clear boundaries, and each service has an independent feature set.

The difference is that SOA can mean a lot of other things. For example, SOA is suitable for a single architecture, focusing on integrating the system into an application and ensuring the reusability of the code. But this is not the case for the micro-service architecture, which focuses on modulating applications by building independent services and ensuring product scalability.

Advantages

Introduce the concept of separation of concerns to achieve agility in software application development, whether in simple or complex areas.

The independence or independence of microservices brings the following benefits:

Services can be built in any programming language, and in addition, a separate data model can be maintained for each given service.

It is easier to maintain by incrementally updating or upgrading the technology stack of one or more services rather than updating the entire application at a point in time.

Reduce risk by allowing deployment of chunks rather than rebuilding the entire application every time a change occurs.

Divide developers into small teams to reduce complexity, each of which is responsible for building and maintaining one or more services.

A fully automated deployment mechanism can be built to ensure the deployment, service management, and automatic scaling of individual services.

The evolution of technology

In addition to the evolution of software architecture patterns, we have also seen the emergence of new technologies such as Docker and Kubernetes to support our software infrastructure and enable efficient management of scalable products and services. We have evolved from hardware virtualization to containerization.

Maybe you think, what does this mean?

Let's use the following figure to understand the development of IT infrastructure:

The first picture shows a physical machine or a hardware server. Typically, we build applications using resources provided by the host operating system, and we use the same pattern when deploying applications. But what if you want to extend the application? At some point, you may need another hardware server. As the number increases, so will costs and other resources, such as hardware and energy consumption.

In addition, you may wonder, is it necessary to use all the hardware resources and operating systems at all times? Of course not. If so, why do you need such a huge infrastructure?

This problem led to the development of hardware virtualization, which led to the emergence of virtual machines (VM), through which we optimized the IT infrastructure. As you can see in the second figure, the virtual machine has its own guest operating system, running on a single physical machine or host operating system. This allows us to run multiple applications without having to install a large number of physical machines. The host operating system ensures systematic resource allocation and load balancing between different virtual machines.

Virtual machines reduce the difficulty and cost of software maintenance, but can still be further optimized. For example, not all applications work as expected in a guest operating system environment. In addition, even if you run a simple process, the guest operating system requires a lot of resources.

These problems lead to the next innovation: containerization. Unlike operating system-specific virtual machines, containers are application-specific because they are more lightweight. In addition, the virtual machine can run multiple processes, while the container runs as a single process. So:

We can run multiple containers on the physical machine, or even consider running the container on a single virtual machine. In either case, it can solve application-related problems.

The relationship between containerization and virtualization is not a competition, but a complement to further optimize the IT software infrastructure.

Docker

Now that we have seen the evolution of the IT software infrastructure, we may want to know how to implement the microservices architecture and containerization discussed earlier. The answer is Docker.

Docker is the world's leading software containerization platform, which encapsulates micro-services into what we call Docker containers, and then maintains and deploys them independently. Each container will be responsible for a specific business function.

To learn more about Docker, let's take the e-commerce site discussed earlier as an example. We know that it has a number of businesses and services, such as creating accounts, displaying product catalogs, building and verifying shopping carts, and so on. In a micro-services architecture, all of these can be treated as micro-services and encapsulated in Docker containers. But why would you do that?

One of the reasons is to ensure consistency between the development and production environments. For example, suppose there are three developers developing this application, each with their own development environment. One of the developers may be running the Windows operating system on his machine, the second developer may be running Mac OS, and the third developer will prefer the Linux-based operating system. Each of them takes hours to install applications into their own development environment and needs to do additional work to deploy them to the cloud. This process is not so smooth, and there is always friction between these applications when they are deployed to the cloud infrastructure.

With Docker, applications can be made independent of the host environment. Because of the micro-services architecture, each service can now be encapsulated in a Docker container. Docker containers are lightweight and resources are isolated, allowing you to build, maintain, publish, and deploy applications.

Advantages

Docker is a very popular software with strong community support and built specifically for micro services.

Compared with virtual machines, it is lightweight and has advantages in terms of cost and resource consumption.

It provides consistency for development and production environments and is ideal for building cloud native applications.

It facilitates continuous integration and deployment.

Docker can integrate with popular tools and services such as AWS, Microsoft Azure, Ansible, Kubernetes, and Istio.

This is the end of the article on "sample Analysis of Docker and Micro Services". I hope the above content can be helpful to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.