Shulou(Shulou.com)05/31 Report--

This article mainly explains "what can Kubernetes do". Friends who are interested might as well take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor learn "what can Kubernetes do?"

What would Kubernetes do?

Kubernetes is an orchestration tool for containerized applications. It is responsible for:

Deploy images and containers

Manage the expansion of containers and clusters

Resource management of containers and clusters

Traffic management of servic

Kubernetes does bring a lot of benefits when your application consists of multiple services running in different containers. For a single application with a static user base, this may be more than necessary.

The task of building, testing, and delivering the application to the container repository is not part of Kubernetes; it can be done using CI/CD tools. In addition to the CI/CD pipeline, Kubernetes can also help you deploy applications to a production environment without causing service downtime.

Improve monomer application

Most applications start as monoliths-putting the entire application in one place so that changes can be made and deployed quickly and easily. However, if your application grows, you need to quickly find ways to scale up.

Does this mean it's time for Kubernetes? Maybe not.

In general, extensions are more about the interior of the application than about high-level architectures and tools. For example, you can scale up the whole by deploying multiple instances using a load balancer that supports similarity tags.

The first step to consider when extending your application is test-driven development (TDD), which ensures software quality and prevents problems as the application grows. Although smaller modules or services are easier to test, modularity also means an increased need for mocking and additional tools for configuration and maintenance. Good testing allows you to build and extend applications easily and confidently.

Configuration management tools such as Chef and Ansible come in handy when you start to expand the whole. You can use them to automatically configure new servers to make sure they are ready to run your application. You can go even further and use tools such as Terraform to help configure new server VM so you don't have to create them manually.

You can also extend other parts of the application when they become bottlenecks (such as databases). For example, if the database becomes a bottleneck, you can move frequently accessed data to a high-performance in-memory data store, such as Redis, to reduce the load on the database.

No matter which configuration management and configuration tool you use, you must have a good CI/CD pipeline. When you deploy the application for the first time, you may have copied the zip file to the server through FTP, but this method cannot be extended. The simplified CI/CD pipeline ensures that your application is built, tested, and deployed automatically without any extra work from you or your team.

You can even use cloud services such as AWS Elastic Beanstalk,Google App Engine or Azure App Service to automatically scale individual applications. All of these bring less administrative overhead than Kubernetes, and they all work well with CI/CD tools.

When developing new applications, focus on developing the best applications. Complex tools like Kubernetes may be the right solution for managing the application infrastructure.

Enhanced monomer application

As the application grows, you may eventually be unable to add functionality to a single application. This is usually because the application is close to the limits of what a single development team can do.

At this point, many teams choose to split single applications and migrate to microservices entirely. Although this is a popular decision, it is neither a necessary decision nor a panacea. Organizations can consider starting with adding functional services for monomer applications, rather than replacing monomer applications as a whole. Some of these support services may actually be micro-services-so you can benefit from using small services under reasonable circumstances while still taking advantage of single applications.

Even if you introduce microservices, you may not need or want to start with Kubernetes. Kubernetes is good at running and extending the Pod of related services and micro-service containers. However, some aspects of adopting Kubernetes are easy to overlook, for example, Kubernetes does not have powerful built-in tools to protect Pod, nodes, and clusters, and deploying Kubernetes clusters in a multi-cloud environment can add a lot of complexity.

Starting with single-cloud platforms like Azure Service Fabric and AWS Fargate, it's easier to start and scale services without forcing you to manage Kubernetes clusters.

Another option is to completely avoid services with maintenance overhead and choose function as a service (FaaS), such as AWS Lambda or Azure Functions. FaaS is a good way to minimize potential infrastructure overhead when adding services to an application. In addition, if you eventually need to use Kubernetes orchestrated clusters, you can use the FaaS feature to enhance it.

No longer use monomer applications

Now, imagine that your monolithic application has grown so fast that you can't adopt a monolithic application, and you need to migrate to a micro-service architecture.

Slowly, you have a variety of services, many of which need to communicate with each other. You need to make sure that interdependent services are always functioning properly and visible to each other.

In addition, you sometimes need to consider running across multiple availability zones (and perhaps even multiple cloud providers).

At this point, you may need a coordinator like Kubernetes. It allows you to easily define modules for related services (Pods), and automatically scale application instances and load balance between services.

For Kubernetes to work, organizations need to:

Operate several or dozens of virtual machines

Assign personnel for special configuration and maintenance of Kubernetes

Automate the deployment of most similar services

Has nothing to do with the cloud (or managed) provider

In addition, Kubernetes has built-in support for high availability (Amazon RDS Multi-AZ) deployment, which makes it easier to improve the reliability and availability of applications.

Of course, this does bring overhead: it takes time and engineering resources to create and manage clusters, define Pod, and create containerized applications suitable for deployment to Kubernetes. However, if your application is large enough to benefit from Kubernetes, then the administrative overhead is worth it.

At this point, I believe you have a deeper understanding of "what Kubernetes can do". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

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.