Summary: 17 experts, seven major trend, Wan word text.
(Author alphabetical order)
Author: tert same, Valley Park, not aversion, infertility Rui, Xu Xiaobin, to Jane, Code violation, Lu straight, corrections, small sword, Tang Zhimin, white Mu, cycling, Wenqing, myself brother, waterfowl, Shenxiu
Over the past few years, it is a native cloud technology and the concept has been widely accepted for years. In this rapidly developing field, it is particularly difficult to predict the future, but we had some of the firm belief that open innovation as the support of native cloud field will continue to reshape the software life cycle, continue to bring value.
2019, the number of hot technology trends, attention, cloud native high, many developers are on a rise all the technology thus very sought after, many companies began to explore native cloud infrastructure transformation landing. In China, developers have gone from a focus on "the concept of native cloud" to focus on "cloud native landing practice" changes.
In preparation for Ali cloud the first cloud-native practice the summit, we started to explore the application and research of cloud native art, we invited 17 cloud-native technical experts calculated from Serverless, Service Mesh, Kubernetes, edge, vessel instance vessel engine, native cloud infrastructure, cloud-native application development 7 development, review progress in the field of native cloud 2019, depicted the new decade native cloud technology.
2020 cloud native landmark event prediction
Looking to 2020, in the field of research and application of native cloud technology, we foresee these landmark event.
First, native cloud technology focus attention on the move, Serverless and application management focus.
Over the past few years we have seen, native cloud technology around the center of gravity of the container and the container arrangement. Docker and K8s success has become almost synonymous with cloud-native. Many people say, Kubernetes is becoming boring, this is the trend for the technology is.
Cloud native is about to move the focus of attention:
Operation and maintenance of automation define and configure applications, and online publishing, becoming the core of the development and operation and maintenance personnel concerned. Alibaba and Microsoft jointly launched the Open Application Model (OAM) is an important project in this direction.
As an extension of the cloud native technology, non-server computing (Serverless) will further release capabilities of cloud computing, security, reliability, flexibility and other requirements implemented by infrastructure, allowing users to only focus on the business logic without having to focus on the specific deployment and operation, dramatically improve application development efficiency, and in this way to promote the social division of labor, cloud vendors can achieve further substantial cost optimization through scale, intensive. I believe more innovation and landing practice emerged in this area in 2020 will be.
Second, native cloud technology as the main front of innovation and competitiveness of the cloud service providers.
Along with container-based native cloud technology has been widely accepted by users, be sure expected, the container will soon become a cloud and the basic user interface. So for cloud service providers, based on container, micro-services, no servers, and other new cloud service grid skilled native, will be the main front in the future innovation and competitiveness of cloud vendors.
Virtualization is the subject of the next three years will be incremental resources on the cloud, but the combination of bare metal and container security sandbox virtualization of hardware acceleration, and the cloud is accelerating the process of container companies. Key to the future competitiveness of the cloud technology vendors in the cloud traditional strengths include size, stability, cost to play to the extreme under the premise, native will continue to innovative technologies and products to serve customers through the cloud to obtain customer approval. Native products in the field of cloud cloud vendors will be intense competition and defend.
Third, native cloud from the cloud to the data center side end integration, will be everywhere.
Cloud technology originated in the native applications and services in the data center, and gradually extended to calculate the end edge of the scene even in the last few years. I believe the future with the rapid development of 5G / IoT, the cloud side end integration of native cloud technology will delve more businesses and more rich scenes, will be everywhere.
Fourth, the enterprise cloud native will experience the pain of landing, native cloud cloud will become a trend.
Cloud technology will lead to the development of enterprise landing speed. Although native cloud technology has been widely accepted, it landed in the enterprise technology stack will still take time, but also faces many challenges. The container of the process of changing habits in the operation and maintenance of the traditional virtual machine model, the traditional application of distributed micro enterprise service-oriented transformation involves re-architecturing other factors.
After being accepted native cloud business, landing procedures need to address these challenges. Operation and maintenance management component and is rich in rapidly evolving cloud infrastructure is also native to the technical skills of IT staff put forward higher requirements. However, we believe, bring native cloud technology to reduce the cost of resources, enhance the efficiency of research and development operation and maintenance and other great value, will drive enterprises to meet these challenges.
In this process, the use of cloud born on the original cloud-based service grid containers and other standard interfaces and hybrid cloud solutions will greatly reduce the complexity of cloud moved, so that enterprises can quickly migrate to the cloud on a standard service. By maximizing the use of cloud cloud capacity and efficient social division of labor on a cloud native to enable enterprises to focus on their business development, we believe will become the consensus of the enterprise.
2020 cloud field Native seven major technology trends
1、Serverless
2019, the industry's ability Serverless major computing platforms have made great progress, it has become more common. For example, completely eliminate the effects of cold start delayed by reserving resources, so that delay-sensitive online applications can be constructed using the Serverless way. Serverless ecological growing. In terms of application building, security, alarm monitoring the emergence of many open source projects and start-up companies, more and more mature tool chain.
User acceptance of Serverless increasing. In addition to quickly embrace new technologies such as the Internet industry, traditional business users are beginning to use Serverless technology. Standing at a new decade, Serverless field evolution will occur as follows:
Serverless further into the online business will deviate from the line of business.
True on the number of requests from zero to a billing and response time is a natural contradiction to FaaS represented Serverless technology from the outset are not sensitive to response time, event-driven business start line deviation. But today we have seen, including AWS Lambda Provisioned Capacity and Azure Functions Premium plan including product features, allowing users are paying a little bit extra costs in exchange for a lower response time. This online business is undoubtedly more suitable.
Serverless not only the ability to use or function will accelerate infrastructure and services Serverless technology.
After hosting service code to Serverless platform, i.e. can enjoy automatic elastic energy charging capacity as requested. But if the infrastructure and related services do not have real-time capability of scaling capacity, then for the whole business, it is not elastic. We have seen around Lambda AWS VPC for network, database connection pool resources such as real-time elasticity done a lot of optimization, we believe that other manufacturers will follow, and then the whole industry will accelerate the Serverless infrastructure and various cloud services.
To Knative as the representative of open source solutions will get more and more attention.
While various cloud vendors are promoting their Serverless product, but developers will still widespread fear is bound manufacturers, so the organization will have a certain scale based on open source solutions, such as Knative, build their own Serverless platform. Once an open-source solutions into the mainstream, cloud vendors will take the initiative to open standards and is compatible with increased community input.
Serverless developer tools and frameworks will further prosperity.
Supporting user tools and services IDE, problem diagnosis, continuous integration / publishing experience will be more complete. We will see more success stories and best practices. There will be an application framework for the Serverless born in the area of front-end development, engineering efficiency will play to the limit.
Java continued onslaught, will be one of Serverless platform for mainstream language.
Serverless platform requirements mirroring applications small enough to be able to quickly distribute, and requested application startup time is very short. While in these areas, and NodeJS Java and Python language gap, but the Java community in the ongoing efforts. We see Java via Java 9 Modules and GraalVM Native Image technologies such as continuous efforts to "lose weight" in the mainstream framework Spring began to embrace GraalVM, and the new frameworks such as Quarkus and Micronaut also make new breakthroughs. Java gives the feeling of looking forward to a new look at Serverless field.
Solve the middle layer FaaS state transfer (acceleration layer) research or product is expected to be a breakthrough.
Serverless at Function scene biggest challenge for the future is the need to function in series between the state (state) passed, function need to deal with delays caused by frequent interaction and external storage such as amplification. The traditional architecture of these are processed within a program process. The need to address these challenges calculate intermediate layer (acceleration layer), calculate the intermediate layer (acceleration layer) is one of the crucial future academic research and product development direction.
Based WebAssembly (referred WASM) of FaaS program is expected to occur.
Docker one of the founders of Solomon Hykes said, "If there WASM and WASI in 2008, we had no need to create a Docker", this sentence to some extent, the importance of WASM. Although the current WASM more as a run being understood in the browser technology, but it has a very good safety isolation, fast startup speed, and support for over 20 languages, so why not let it run the service side of it? These are very technical characteristics fit the requirements of FaaS.
2、Service Mesh
In 2019, Service Mesh overall solution is gradually emerging oligopoly situation. One solution could be universally recognized by the industry, the key lies in its technical team if there is a profound insight into the complexity of distributed control applications, and the ability to create a de facto standard for cloud vendors have all been adopted. De facto standard for customers to use the Service Mesh, it means that distributed applications can be easily deployed on a cloudy and hybrid cloud according to their needs.
Standing at a new decade in 2020 Service Mesh areas will have the following changes:
2019 Service Mesh heat continued to rise, landing issue will be resolved in 2020.
2019, Service Mesh in some companies such as ants gold dress usher in large-scale landing, the industry's popularity continues to rise, greatly increased the confidence of domestic companies for Service Mesh, now almost every little larger Internet companies We have started to practice Service Mesh, including the US group, headlines, Baidu and other companies.
Of course, in 2019 the industry landing a variety of problems, including the problem Sidecar large-scale operation and maintenance, etc., in order to OpenKruise / kruise is represented SidecarSet although some efforts have been made, but there are still Pod upgrade process is too complicated the problems, which are expected to be resolved in 2020.
Istio will be more mature, more suitable for landing large clusters.
In 2020 Istio as a control plane technology will continue to play a central role in the field of Service Mesh. Istio obtain reasons for the industry's attention, and that backed Google's internal engineering practices, as well as the practice of rethinking and re-engineering of refining. Istio important work in the past year is to improve the functionality and improve the stability to ensure that small-scale production is available, providing real scene with Alibaba use of large-scale use of this technology for large-scale landing will Istio in 2020, which will Istio make a substantial increase in their ability to support cluster size in the next year.
In addition, with the exploration, rationality can Istio operation and maintenance and infrastructure in 2020 will usher in positive change, deploy and complexity of higher operation and maintenance problems will be resolved. Istio Envoy adopted open source projects in the new year remains the de facto standard for data plane of the Service Mesh leadership, Istio Envoy and the open source community because two close collaboration and better promote the Service Mesh evolution forward.
Serivce Mesh on EdgeService heat sustained Service Mesh & IoT.
2019 Serivce Mesh on Edge in the heat gradually upgrade, the Edge is essentially to provide a faster response to enhance the experience. For Service Mesh, it was placed under the "comfortable" cloud Edge, to solve the performance, low resource consumption, security, high availability and other issues, specifically Kernel Bypaasing, Sidecar as Node + WASM, SmartNic hardware and software, IoT Identity combine , secret protection, low output costs, non-reliable network environment, the current look is still very challenging, these issues will be part of the solution in 2020.
More Than Service Mesh。
Service Mesh decoupling applications as a key technology and infrastructure, and in 2020 there will be more products by binding to complete BaaS Service Mesh technology, which in addition to reducing unnecessary duplication, but also makes the cloud because those products and applications stripping out irrelevant content to sink as part of the infrastructure and accelerate its speed of evolution, as well as to the user's cloud offerings bring even better software development and maintenance experience to accelerate exploration business efficiency and reduce exploration costs.
We saw Envoy also provides protocol support for MySQL, Redis, MongoDB, DynamoDB, it is possible to resolve support requests, request-level statistics, failure statistics and other general observability characteristics. Follow Mesh will continue to evolve into a whole network infrastructure level, to control all aspects of the application / inlet flow.
Prospects for 2020, Service Mesh prerequisites will be resolved in the direction of a heterogeneous communication systems, hybrid cloud architecture, etc., in the hybrid cloud, old and new architecture scene, and Service Mesh binding capacity of the existing infrastructure will become Service key Mesh landing, such as support for VM scenarios, support for traditional service registry and so on, I believe there will be more value to the company through practice and somatosensory service Mesh is more, by creating more customer success stories and Mesh accelerate the popularization of Service. Perhaps 2020 will be the popularity of the Service Mesh.
3, Kubernetes
2019, in continuing to promote community participant's head, "scale" and "performance" has finally become an important keyword Kubernetes project, which not only opened up last Kubernetes in an enterprise production environment of large-scale landing in the true sense km, but also to Kubernetes for the first time became the protagonist of technology "double 11" and other top Internet-scale scene real.
Standing at a new decade, in 2020 Kubernetes area will have the following changes:
Kubernetes and cloud computing will become the new user interface.
With the popularity of native cloud computing, more and more application workloads are deployed on Kubernetes, including databases, large data, AI intelligent and innovative applications, Kubernetes native has become the cornerstone of cloud computing. Thanks Kubernetes large-scale application management capabilities, ability to support hybrid cloud cloudy, in the year 2020, Kubernetes and cloud computing will become a new user interface. From an architectural perspective, Kubernetes become IaaS layer control plane, and to further underlying IaaS (computing, storage, network) the ability to optimize to meet the order of twelve high density and high dynamic requirements of the container brings.
Kubernetes ability to control the operation and maintenance team to become the core business skills, and promote the development and AIOPS each other.
Whether large-scale use Kubernetes will bring unemployment enterprise operation and maintenance personnel? In fact, as more and more enterprise IT infrastructure, from on Kubernetes to in Kubernetes, a large number of CRD, Custom Controller and Service Grid introduction to stability and performance optimization Kubernetes bring a lot of challenges. Grasp the depth of Kubernetes gradually become an important operation and maintenance team to assess the scale of the enterprise technology capabilities, operation and maintenance personnel and business skills will be the data from the automation and intelligent development.
Forecast in 2020, around the Kubernetes of AIOps will gradually pouring, to further improve Kubernetes cost optimization, fault detection and optimization cluster.
The Kubernetes and other native cloud technology also makes AIOps no longer smoke and mirrors:
1) Thanks to well-designed Kubernetes, including declarative API, immutable architecture, elegant extension mechanism, you can publish and promote the application of operation and maintenance operations normalized (Normalization);
2) in conjunction with GItOps, Tekton, SecOps automation lifecycle process of landing, the application of more standardized (standardization);
3) with the advance OpenTelemetry, CloudEvents and other projects in the field of application observability logging, monitoring, field Tracing, events further standardization and integration, making multi-index, root cause analysis of richer data set to improve AI level AIOPS accuracy and coverage.
New kernel, new hardware help optimize container Evolution OS.
Container technology after years of development, from early Docker, rkt, CRI-O, etc., to containerd, Kata Container, gVisor, has become an important cornerstone Kubernetes run. But both the further isolation runc scene, or further optimize the performance of security containers scene, but also need to continue grinding and enhanced.
With the new core technologies include CGroup V2, namespace, virtiofs etc. matures, can further enhance the ability of the container operation. On the other hand, some of the new hardware includes the introduction of NPU, MoC, NUMA, etc., but also brings more to optimize space and scenes container and K8s scheduling. Thanks to the addition of these capabilities, tailored to the scene container container optimize the OS as possible, and will be rapid development.
Container Mesh network and the network will be further integration.
Service Mesh After years of market development in 2020 will be popular in Service Mesh technology. The Service Mesh performance optimization will become the main event, a number of programs have also been selected to sink further optimize network performance based on forward CNI (container network interface) and the kernel technology.
And the container is gradually evolved network itself, from face to face the Identity ip, from a single to multiple containers network plane network plane, and further optimize the network performance and zero forward trusted security. In 2020, we believe container Mesh network and the network will be further integration, further integration in Network ServiceMesh, NFV and other scenes.
4, the edge calculation
With the advent of the Internet era and 5G all things, the number of networked intelligent terminals will increase dramatically, the traditional centralized computing center cloud storage, computing model has been unable to meet the terminal device for aging, capacity, calculate power requirements, the ability to cloud computing under sink to the side edge of the device side, and delivered by a unified center, operation and maintenance, management and control, will be an important development trend of cloud computing.
IDC predicts that by 2020 the world will have more than 50 billion of terminal and network equipment, more than 40% of the data to be analyzed, processed and stored in the side edge of the network, which provides sufficient edge computing scene and imagination.
Standing at a new decade, 2020 computing edge will have the following changes:
To Kubernetes native cloud-based technology, after years of rapid development, the scope, landing scenario, technology maturity, etc. has made great progress, one of its core values is achieved on any infrastructure to provide unified standards and on the cloud consistent functionality and experience. The cloud-native technology and edge computing combined, can quickly achieve "cloud - edge - end" application distribution integration to solve the massive side, on the end device will be finished large-scale application delivery demands of operation and maintenance, management and control;
security aspects, cloud native technology can provide container and other safer work load operating environment, as well as the ability to flow control, network policy, etc., can effectively improve the safety edge services and edge data;
in the lower edge of the network environment, the edge of the cloud native technology container capacity, to ensure the autonomy of weaker net, off net, providing effective self-healing ability, and good compatibility with the complexity of network access environment;
relying on cloud native areas of strong community and vendor support, cloud-native technology the applicability of heterogeneous resources gradually, in the areas of networking, cloud native technology has been able to support a variety of CPU architectures and communication protocols, and achieve low resource usage.
There are already many manufacturers try making cloud native edge computing, and has been part of the success stories, I believe that with the rapid spread of 5G, native edge computing cloud development will be greatly accelerated in 2020.
5, the container and container instances Engine
In the last month of AWS 2019 years was finally released Fargate for EKS products, which also declared Kubernetes use container instance Serverless as the underlying runtime resources on cloud products form the industry has been more widely recognized. As an example of the container by the underlying runtime entity that allows users to focus on building their business and services, no longer need to configure and manage the servers, out of the complexity of infrastructure maintenance. At the same time to reduce user costs through real pay-and real-time expansion.
Whether Amazon Fargate, Microsoft ACI or Ali cloud of ECI, each product is currently on the specific architecture docking Kubernetes still have differences, to provide full support for Kubernetes function in Fargate as the representative uses a pass-through mode Node information ; to ACI / ECI is used as the representative virtual kubelet butted Kubernetes container instance management.
But whatever the docking way, examples of the core container products still need to build on the flexibility, cost and Kubernetes compatibility. To achieve customer service through real-time on-demand elastic expansion, users do not select the instance and cluster capacity, you do not need to pay for additional server and preset; to achieve real-time expansion of the real pay-per-use resources, reduce the cost of users; Kubernetes has become fIELD container arrangement facto standard, compatibility Kubernetes function determines the scope of application of container instance.
Standing at a new decade, I believe will continue to improve product container instance in 2020 in these three areas and improve, continue to improve resilience capacity, reduce user costs, and continue to improve the integration with Kubernetes. There will also be more migrate to cloud-native applications on + container instance Kubernetes, enjoy cloud-native technology bonus.
From the manufacturers of similar products, we can also see this in the design of products in common:
One example corresponds to a Pod
docking Kubernetes
containment vessel as the underlying engine
This is where the use of safety as the underlying container vessels of various engine is very important underlying ability. In 2019 the isolation container security technology is increasingly valued as a spacer layer, not only to enhance the security of cloud-native platform, but also have a significant effect on the operation and maintenance can be, quality of service and user data protection. However, early return to the heart, the user selects the cloud is essentially a native container to bring agility, they can quickly schedule and launch container, and the flexibility to use resources in this regard safety technology still can not reach the level of conventional containers.
Whether Kata Containers or gVisor, open source container security engine in 2019, have made a lot of progress, Kata Containers clearly stated that "doing virtualization for cloud-native" as the 2020 target:
Sharing of resources among the sandbox, while maintaining the sandbox boundary is still clear.
Real-time, dynamic on-demand resource for the sandbox, rather than as a fixed resource allocation as partitions.
Host userspace tools, VMM, and the application of the core together, cooperate with each other to provide services for the sandbox application.
In 2020, the virtualized container on behalf of the Kata will be traditional virtualization lopsided and more "Application Center", gVisor as the representative of process-level virtualization also expect more for optimizing applications. We believe that in 2020, we do not have a unified secure container technology, but the first years of the 21st century, 20 years, and we look forward to the common development of hardware and software will make the mainstream of container engine has better isolation sex.
6. Infrastructure Evolution
Based Serverless Infras Architecture Evolution Kubernetes has been the focus of major cloud vendors and community concerns. December 2019 AWS held in Las Vegas, the annual re: Invent conference announced the EKS on AWS Fargate product officially GA, the news set off a firestorm in the cloud market and in the community.
After the EKS on Fargate provides a standard Serverless Infra. User experience that users purchased EKS services, eliminating the need to purchase additional Infra cloud resources (such as VM, Nitro), you can use the native K8s API to deploy their own applications, and supported by the amount of billing.
. Serverless Infra architecture enables the user need not be concerned detailed facility computing, networking, storage and other underlying, really allows users to return to for POD application resources deployed shape up; at the same time control and data planes strong isolation capability will be Serverless Infra architecture. the key, in addition to user details underlying the outer shield facilities, Serverless Infra. need to provide the user with a safe and reliable tenant isolation environment
2019 With a comprehensive cloud on the economy, lowest scheduling system, a comprehensive upgrade to the cloud native Kubernetes + lightweight container architecture evolution, and large-scale deployment on bare metal instances dragon; at the same time becoming operational technology-based security kata-container when the container mature, poised for large-scale roll out.
Standing at a new decade, is expected in 2020, will be the economy towards a comprehensive infrastructure Serverless Infra. Year, Serverless Infra. + Security architecture will be based on the Dragon container architecture, by constructing hard / soft multi-tenant capabilities, capacity and highly resilient self-healing capacity of the container, to provide users with the ultimate in security, stability and user experience of isolation. At the same time the underlying pool of shared resources can effectively improve the overall resource utilization, and the exchange will pool resources to effectively reduce the overall cost of the machine
7, Application Development
Looking to 2020, we believe that cloud + native intelligence will become the next generation of research and development platform two most important characteristics, will further reduce development barriers by adopting complex technologies and tools released by productivity. When all complexity are offloaded to the cloud, we will go back to 10 years ago when the efficient development of stand-alone program.
Standing at a new decade, 2020 following the evolution of application development will occur:
From Web-IDE evolved into Cloud-Native IDE
2019 is the VS Code ecology pulling ahead of the year, thanks to its modular design, VS Code in several core components of Monaco editor, plug-in system, Language Server Protocol (LSP) have become the standard Web-IDE Selection. Communities there have been code-server-based VS Code so pull up Web-IDE command line program.
In addition to the VS Code, Theia also continue to evolve, especially those based on gitpod.io bright spots Theia by the gitpod buttons integrated on the page, such as GitHub README, a key to achieve from the code to preview the smooth experience.
On the other hand, manufacturers of existing Web-IDE program also need to go back to embrace the community, such as Facebook entirely from thorough self-development Nuclide turn toward VS Code, and whether the Amazon or Google has not yet Cloud9 external Cider, if to further the commercialization, support VS Code plug-in system presumably is taken for granted.
From the Local-IDE to Web-IDE it reminds me of the year from the PC to the mobile terminal. Today though, a lot of professional tools of the PC experience is still difficult to match the mobile terminal, but the dominance of the mobile terminal already beyond doubt.
Web-IDE has out of the box, controlled and consistent environment and other Web services to seamlessly integrate natural advantages. In addition to continuing to do next and Local-IDE filled in the gap between the outer end functions can also be combined to build a distributed compiler, centralized code repository, massive code index analysis, cloud collaboration, to provide a true Cloud-Native IDE.
Tools -> Platform -> Standard
GitHub this year launched GitHub Actions, the flexibility to integrate various third-party services in the workflow through it. GitLab also earlier when it launched a customizable CI pipeline configuration. Whether GitHub or GitLab, they are from the early simple code hosting a one-stop tool for growing DevOps platforms.
IntelliJ started at the earliest tools are no longer satisfied with merely polished JetBrains IDE, also launched the Space this year, trying to build a one-stop platform for R & D team. Order entry tube tool Jira started Atlassian, it has been a self-development to keep pace with the acquisition of two carriages, again this year through the acquisition of territory on their own research and development platform for increased management perspective Jira Align.
A rising star known as sourcegraph altogether directly on the site that they are The new standard developer platform. Whether based on Dev tools right, or left Ops it is based tool, when the tools were all more or less grown into a so-called one-stop DevOps / DevSecOps platform.
Then the next, on top of these platforms if you can extract the common standards? For example CI field, if you can define a set of CI pipeline can dominate CircleCI, GitLab, GitHub Actions like? Whether a set of standard workflow allows users seamless migration between AWS Step Functions, Argo, Tekton?
At a higher level of abstraction, such as Open Appliction Model (OAM) such a standard is not able to really build a bridge from the business architecture to infrastructure. Although today's R & D platform is already relive the situation, but in the cloud native, standard first idea, I would expect a standard from the native cloud service layer closer to the entire series from R & D platform.
Developer Tools collaborative work from the local to the cloud
The current developer tools are used in the vast majority of lift and shift the cloud from the local translation, or products designed for single human-computer interaction, moved to the cloud development tools have not make good use of the cloud multiplayer real-time interaction Ability. Whether it is more than collaboration (cloud has made us closer from each other), or human-machine cooperation (cloud has allowed the machine to become stronger), I look forward to further tap the emergence of cloud collaboration capabilities of innovations.
More research and development platform for the emergence of native cloud
To Kubernetes, Serverless, Service Mesh, Cloud IDE, represented by a number of native cloud technology is impressive in the past year. We were surprised to observe, to small and medium companies on behalf of the Internet technical community began to rapidly embrace this technology system, and through the cloud landing native, fast access to the Internet in the past manufacturers have elite software delivery capabilities, such as sophisticated traffic management capabilities , gray-publishing capabilities, a / B Test capability, multi-environment management capacity, infrastructure key to pull a fast scaling capabilities, and so on.
But at the same enterprise adoption of new technologies, but also we face many challenges, such as open-source software to build a complex process, black-oriented interaction design, lack of R & D management methods, the lack of enterprise rights management capabilities. Therefore, a large number of software vendors start of native cloud-based technology system development related management platforms, such as QingCloud, Rancher, Ali cloud container services. As a leader in R & D collaboration platform on the cloud cloud effect is also actively CICD tools, test environment management, application operation and maintenance concept, DevOps collaboration with the methodology and other native cloud technology through integration, providing new technology solutions out of the box Program.
Data and intelligent tools era
Cloud native is an open standard technology system, is the core contributor to the world of the Internet giant enterprise cloud vendors. With the enhancement of development and influence of technology, technical barriers to private enterprise will gradually break and begin to adopt cloud ready cloud native products to transform their technology systems. Convergence technology has brought the possibility of a unified specification data, and the data is the cornerstone of all intelligent.
We observed the last year AWS, Microsoft, Facebook, ebay and other manufacturers are actively layout smart tools, from the traditional "code" smart tool gradually extended to the "service" smart tool. Such as the recent release of AWS CodeGuru, it is a code review for automated performance optimization and machine learning recommendation service. It can identify the lines of code that most affect the performance of the program, and provide repair or make specific recommendations to improve the code. This is the service of large data intelligence tools combined with large data code and runtime.
2020 How to honor the new technology to bring business value
For cloud native practitioners, 2020, the biggest challenge may be to honor the value of new technology to bring the business. Although there are different levels of the past year, interpret different perspectives on the value of cloud-native, but more still from a technical level, few walks of life customer success stories elaborated direct business value of new technology brings.
From the perspective of the market: there are still a large number of enterprises in traditional industries in a physical or virtual machine age, influenced by the condition of the assets of their core business it's hard to move onto the cloud native and appreciate the tremendous value of new technologies; other on the one hand, for those companies already entered the era of the container, over the years they continued to invest in software assets on a lot of resources to do the construction, from the functional level has already established software assets and cloud native equivalent, will not soon from self built into a cloud-native. This is the normal attitude of the market before the face of the popularity of new technology, industrial customers are being changed from both ends, they have gradually reached a consensus figurative cloud native of this concept today.
Standing at a new starting point for a decade, cloud native practitioners should strengthen our understanding and insight into the value of new technologies, sink the heart to the cloud native capacity building good foundation. At the same time, we need special attention in an appropriate manner and timing of cash to business value through more customer success stories to accelerate market acceptance of new technologies, so that their results faster and better recognized by the market, and create industry trends, to make its own contribution to the development of cloud computing.
