Analysis of DevOps Development trend: Architecture Chapter __devops

In the practice of devops, what should be paid attention to from design considerations.
Hybrid cloud infrastructure will be a trend in a short period of time

Over the past 10 years, cloud computing has driven a massive transformation of the data center. In the early years, many organizations struggled with the lack of a good architecture for scaling up the underlying framework, after getting the machine hardware, the installation and configuration often takes months, and once the data center is created, the updates and maintenance become a bigger pain point, and the Operation team has to install and update the patches on a single machine.
Many cloud service providers, such as Amazon and Ali Cloud, make it easy to obtain services for computing virtual machines on demand. Almost all of the current private cloud or public cloud support the use of API for fast and easy configuration and management, traditional manual or can not standardize the operation of large-scale processing instantly become extremely easy, efficiency and speed greatly increased.
In addition to native cloud services, tools such as Ansible/chef/puppet have made the landing of infrastructure as code (IaC) a reality. In the end, the entire data center can be in the form of code, version management, and automated deployment and change management.
Due to several factors, the private cloud and public cloud will exist in a short time, and become a trend for some time.

Factors	Detailed Description
Safety	Part of the security data due to the enterprise's own security considerations or legal compliance requirements and other reasons, cannot be placed on the public cloud, while the current cloud service provider's vendor lock is more likely, and many companies are handling the core business using enterprise private cloud in order to avoid core functionality from being subject to the provider
Cost	In order to be able to continue to play a greater role in the old hardware, the use of existing hardware to form a private cloud, but also to improve ROI, save costs, directly discard existing hardware is not realistic
Old system	The old system runs in the original hardware environment within the enterprise, even if the unified use of the procurement of external cloud services, there will be an old system porting transition process, according to the actual situation, this transition period will often continue for some time

The system architecture requirements under the Internet + will become standard

It's an era of software dominance, and application software is incredibly important to every business. Companies such as Amazon/netflix/uber have subverted the traditional business model, largely relying on its powerful hardware and software capabilities. While not every company can transform itself into Amazon/netflix, as technology advances, the features that these companies can now embody are likely to be standard in most companies ' applications in the near future, such as 24x7x365 high-availability, and no downtime to support massively high concurrent workflows Ability to scale horizontally or horizontally to fit the needs of a complex infrastructure, including load balancing, rapid updates and continuous feedback from firewalls and security mechanisms to reduce risk and promote and drive innovative and better features to support development and operational teams to avoid publishing problems Faster and more stable service development and delivery of micro-service decoupling architectures will become a trend

The micro-service approach is very similar to the traditional SOA, aside from the concept debate, let's rethink the problem of a single application that is overweight in a traditional business: Over the years, this inherently huge system will eventually form a domino that no one can easily move: the cost of the changes is huge and the expansion is difficult.
Instead of using micro-service, by simplifying/miniaturization the function as far as possible, delineating clear functional boundaries, reducing the coupling with other modules, and interacting through the normalized lightweight restapi, the deployment of the service can be replaced so that the overall impact is small, even if the problem can limit the scope of impact, In fact, this approach is often considered in the traditional SOA architecture design, but before the DevOps campaign, the deployment of these elements are not covered, in addition to micro-services compared to the slightly larger and heavier, such as many micro-services used in the RESTAPI, Used more soap and more. There are also a number of open source frameworks that can make micro services faster when they land, for example, using the many out-of-the-box features provided by spring Cloud, service registration, API gateways, load Balancing, configuration centers, etc. are available, and we only need to focus on the implementation of business functions, which greatly improves efficiency.
Micro-services bring clear boundaries and controllable impact, and there are many other problems that are not. A friend of the micro-service in a project said they implemented the micro-service, the biggest advantage is that the previous deployment of a package at the end of things now need to do 20 times. Although it is a joke, it also shows a fact. Micro-service is designed to decouple business functions into small units that can be deployed independently, but with the increase in services, these will have a lot of impact on management. Micro-service practices without devops practice are simply unthinkable, and this decoupling approach will become one of the popular architectures in DevOps practice. the container will become the trend and direction

Containers make delivery more transparent, convenient and efficient, while using containers to implement the various levels of environmental consistency advocated in DEVOPS practices: Development environment/test environment/production environment consistency.

Project	Detailed Description
Development environment Consistency	Using containers ensures a consistent development environment, ensures that all members are developed in a consistent environment, and avoids rework caused by various versions.
Test environment consistency	Use a test environment in which containers can be consistent to avoid the possibility of non-defective validation of environmental problems and the timing of the delay and delays in the defects.
Production environment consistency	The use of containers ensures that the quasi production environment is able to obtain the test elements that are as similar to the production environment as possible, while avoiding problems caused by changes in hardware and software.

Container-related has gathered mature levels of the ecological chain, a rich variety of mirrors, there are various levels of container management tools, there is a partial IaaS layer, but also the orchestration of the PAAs layer, such as kubernetes tools. Summary

DevOps is not just ci/cd and tool chains, in order to promote the landing of DevOps practice well, the architecture of the system must also be considered, and this article discusses some of the architectural trends and orientations that need to be considered in the context of the current situation, including the characteristics of the infrastructure and good systems, as well as micro-services and containers. But it's not conclusive, for example, micro-service can be decoupled, but the coupling will not disappear, only in another form, when there are thousands of design is not very reasonable in the overall framework of micro-service composition, but also want to understand the composition of the whole, it is difficult to assert that this architecture will be another nightmare But technology is always evolving, looking for hope in desperation, never giving up, and one day we will be saved.