Cloud native definitions and rules
Creating software is designed to use cloud resources should be the next major step migration organization.
People usually have a love-hate relationship of the popular terminology. On the one hand, it is often seriously abuse, virtually lost all practical significance. On the other hand, they seem to be the only way to succinctly convey certain concepts.
Cloud native is such a buzzword. Recently, everything and nothing seems to have marked a native cloud. Do not believe it? Google the phrase "cloud native hardware", "native cloud marketing experts," and "accounting firms cloud-native." It's an epidemic.
However, it should also be clear how to talk about a new wave of software running on the target public cloud platform is built? Seems to be no better label. Although people have a certain affinity for the recent popularity of "modern cloud applications," but do not think this is a step forward, but it is seriously considering how to enter this field.
As adopted a very different approach to protecting these new types of security applications start-up companies, even if not useful to talk about changes that have occurred, then began to explain how people work?
Therefore, it is necessary to try to cloud the meaning of the original agreement. Technology has many definitions, most of the definitions are too detailed, but surprisingly useless. For people to understand the term cloud native most useful way, when people regarded as the cloud platform operating system, cloud native is the whole philosophy behind it.
Historically, people use cloud computing as a way to consume virtualized hardware, such as computing, storage, networking. When the enterprise "cloud-native", and can enhance the level of design, build, deploy, and run the software depends on the cloud platform to provide companies can take advantage of the wealth of services and useful abstraction, making it easier to consume these services.
Like with any other operating system, it can prevent companies want to worry about managing their storage resources to match and handle many applications in complex tasks and other issues of common processing requirements and hardware core. And any other operating systems, companies often know more information about what you do not want. Like any other operating systems,
This is the principle thing ......
The following look at some of the key principles derived from the above-defined cloud native software.
Whenever possible, use hosting services
If you like Windows, like AWS, then the Kinesis DirectX imagine it. If companies are looking to build games for Windows may not launch its own graphics rendering engine. Companies will use the function of the native platform to provide. If companies are looking to collect and process real-time streaming data, we should not stand on the complex pipeline on the machine EC2, but should try to use Kinesis.
Let cloud computing providers deal with the health and expansion
Avoid the need for companies to monitor the health and load handling and extensible architecture. These are complex issues involved in performance and cost, they are the bane of existence for most organizations. Modern cloud platform more and more to get rid of these problems. AWSLambda and GoogleCloudRun services allow businesses to run code without processing extension and health. And other AzureBlob or AWSS3 storage service that lets businesses forget the capacity and throughput. This makes your application more flexible and make operation easier.
Code applies business logic
Write code should be a last resort, and should be mainly used to achieve valuable business logic. All other content companies should be required API calls. If it's not core, then other people have built it. Use them. They may look more expensive, but companies need to consider its cost, not only to write code, but also to test, maintain and operate it.
Do not worry about vendor lock-in
This is very important. When writing software companies, if you need to switch platforms, to think what will happen is not wrong. But if some things in order to avoid the use of future platforms may not be present while their applications paralyzed, then the business has at least ready. For public cloud, which is even more obvious. Enterprises are never locked in on one platform. Enterprises always be part or all of an application to another cloud platform. So, just focus on getting the maximum benefit from the enterprise platform of choice, and do not over-emphasize when companies decide to move what happens.
There DevOps, CI / CD, agility and twelve factors
This is another thing that people do. They all have their favorite mix. Building software There are many good trend. If the business is not all can (including security) to modern automation CICD pipeline, it will suffer in the future. Although these things are not directly related, but that does not mean companies should not follow them. It just means that even if companies are building a cloud of non-native software, but also should pay attention to them.
in conclusion
As the saying goes, if you can not beat them, we will join them. If you are building cloud native enterprise software, you can use the native cloud processes and native cloud architecture, and do not forget some of the native cloud security, cloud and cloud coordination generate original native operating.