There is never a shortage of hot solutions in the technology world, and as developers, we are always attracted by cool new technologies, expecting these new ideas to help us deal with technical challenges and business problems.
The problem, however, is that until a new technology is mature and widely used, it is difficult to tell whether it is really the best choice for our use case.
So it's not a bad thing in itself that a technology becomes mainstream, and then the standard of the future - we gain reliability and convenience, even though a tinge of excitement is lost to explore the possibilities (and pitfalls).
As the technology matures, simpler APIs, richer libraries, wider community support, and even technology-related things like training and certification come along. Mature technology allows us to spend more time focusing on solving high-level problems, rather than wrestling with complex technical concepts and low-level infrastructure, in other words, we no longer need to repeatedly try to obtain the details of best practices.
A prime example is Kubernetes, a technology that has been in the limelight since its inception, and recently seems to have crossed the threshold of mainstream or not.
The "leap" of Kubernetes
Earlier this year, Kubernetes became the first project to graduate from the CNCF incubator. Experts generally believe that the "leap" of K8s benefits from the following three points -
First, Docker donated its container technology to the CNCF in early 2017, and the Docker container platform core runtime became a community-owned project that helped establish the industry standard for containerization.
Secondly, the world's major cloud service providers and IT vendors have chosen Kubernetes as the default container orchestration tool, and many of them have launched their own Kubernetes solutions , platforms and cloud computing hosting services.
Third, CNCF launched the Kubernetes Conformance Certification Program to help vendors demonstrate that their solutions are Kubernetes-compliant — giving customers confidence that they can adopt Kubernetes without being locked into a single vendor.
"Boring" is business
If Kubernetes has entered the world of "certifications" and "best practices," does that mean it's no longer a hot emerging technology? Or in other words: Will Kubernetes become "boring"?
Many experts believe that so-called "boring" is not a bad thing. Kubernetes has won the hearts of container orchestration enthusiasts, but in order to survive in the wider world, it needs to attract people who don't spend too much time learning the complex technical concepts of Kubernetes, precisely the people who will be in the next few years. People who use K8s to solve real business problems in the middle of the year - for these users, being able to quickly get the technology to work and get it working is critical.
That's why CNCF is setting out to build a series of training and education systems, not just for Kubernetes experts, but for a broad range of developers. If we just want to leverage Kubernetes to orchestrate containers, that's enough.
"boring" is simple
In addition to certification and training, more and more managed services provided by various cloud computing service providers and Kubernetes solutions that are easy to understand and do not require special learning have also made Kubernetes more widely used.
As developers, our first priority is to build applications and get them running. We might end up being k8s-savvy experts, but that's probably not something we're going to do on day one. The solutions, tools and platforms provided by cloud computing service providers are here, and we don't have to worry about how to configure kubernetes, how to maintain, how to optimize, and so on from the very beginning.
More than just cloud-native apps
Kubernetes isn't just for new cloud-native projects, it can also be used to modernize legacy applications. Through the containerization transformation of legacy applications and the orchestration of Kubernetes, we can break the limitations of the original application architecture and transform into a new model whose architecture adapts to application needs.
The revamped application can take advantage of cloud-native advantages such as elasticity, scalability, and powerful routing, logging, monitoring, and security tools, and we can add new microservices on top of it to achieve extended capabilities.
Explore new "excitements"
If Kubernetes has become very mature and a very good solution, where should developers who like to "tinker" look for new "excitements"?
Think the popularity of Docker containerization solutions paved the way for Kubernetes, which unlocked the Service Mesh microservices architecture... Perhaps as more and more organizations put Kubernetes into production, connecting, managing, and securing microservices capacity will be the next challenge to be solved.
Rainbond is an application-centric open source PaaS that deeply integrates Kubernetes-based container management, Service Mesh microservice architecture best practices, multi-type CI/CD application construction and delivery, and multi-data center resource management and other technologies to provide users with cloud-native application full life cycle solutions, build an ecosystem of interconnection between applications and infrastructure, applications and applications, and infrastructure and infrastructure, to meet the needs of agile development and high efficiency to support rapid business development. Operations and lean management requirements.