Nowadays, all walks of life are embracing the cloud, and we can also hear more and more terms appearing in it. In this issue, Jesse wants to lead you to understand related fields, and talk about cloud native, cloud support and cloud-based.
This article only represents personal opinions, if there is any bias, please forgive me~
cloud native
Cloud native was born in the cloud. Cloud-native applications are built from the ground up and run in public clouds such as AWS and Azure using cloud technologies. These cloud technologies allow for accessibility and scalability, and allow developers to continue to deliver new services faster and easier. Cloud native consists of continuous integration, orchestrator and container engine. At the end of the day, it's about how applications are created and deployed. Cloud native is a new way of building our applications and infrastructure; we are breaking down services into smaller and smaller parts and reusing services as much as possible. Because we need to deploy our applications and infrastructure in other people's data centers, we must ensure adaptation and compatibility issues, so deploying new, flexible, and elastic cloud-native applications is a more appropriate choice.
cloud support
Cloud-enabled typically refers to applications that were built traditionally and then migrated to the cloud. These applications were originally designed in a monolithic fashion and depended on local resources and hardware. In the process of applying to the cloud, the application is reconstructed to use virtual resources, but the underlying architecture remains unchanged. We explain it vividly, this is like a house. A house built 30 years ago is now undergoing modernization, such as a new solar system on the roof. Although retrofitted, in general, the application cannot leverage shared services or resource pools, making it difficult to provide the scalability and elasticity of cloud-native applications.
cloud based
Cloud-based is the middle ground between cloud-native and cloud-enabled. This is an approach to consider if we want to take advantage of certain features of the cloud, such as higher availability and scalability, but don't want to completely redesign our applications to use cloud services. For example, if we move our internal web application to an AWS or Azure server, we now have a "cloud-based" application. After moving the application to a cloud provider, we are no longer responsible for managing the application's resources, so there is no need to maintain servers or worry about backups. We also only pay for what we use. The biggest advantage of moving an application to the cloud is its ability to scale quickly to meet surges in demand and increase application availability.
Compare
We look at the differences between the three from the perspective of design, implementation, maintenance and cost. From a design perspective, cloud-native uses a microservices architecture because it has to account for failures, so applications must be designed to handle different failure domains. Cloud-based applications are hosted on traditional servers in local data centers and are designed for availability. From an implementation perspective, cloud-native deployments are faster because there is no hardware or software to deploy. Cloud-based applications are slower due to hardware configuration or software settings. From a maintenance perspective, applications under the microservices architecture are flexible and scalable, and areas of the application can be upgraded without interruption. Cloud-based applications are tightly integrated, and the entire stack may need to be upgraded, causing downtime. From a cost perspective, cloud native is generally cheaper because we pay the license and storage costs at the cloud provider. Cloud-based applications because we have to own the entire stack and may need to purchase hardware, power and cooling before deploying the application.
Introduction to CnosDB
CnosDB is an open source distributed time series database with high performance and high usability, which has been officially released and fully open sourced.
Welcome to pay attention to our code warehouse, one-click three links: https://github.com/cnosdb/cnosdb