Hey all, this is my first English blog. You will also see me when im blogging about cloud development and micro services architecture in English.
First blog is about Cloud Native Architecture. I will be sharing notes about my development environment, tools and principles. See you around.
Cloud-native is an approach to building and running applications that fully exploits the advantages of the cloud computing delivery model. Cloud native is about how applications are created and deployed, not where.
DevOps is the collaboration between software developers and IT operations with the goal of constantly delivering high-quality software that solves customer challenges. It creates a culture and environment where building, testing and releasing software happens rapidly, frequently, and more consistently.
How Does Cloud Native Work?
The fundamentals of Cloud Native have been described as container packaging, dynamic management and a Microservices-oriented architecture, which sounds like a lot of work. What does it actually mean and is it worth the effort? We believe Cloud Native promotes five architectural principles:
Use infrastructure-as-a-service: run on servers that can be flexibly provisioned on demand.
Design systems using, or evolve them towards, a microservices architecture: individual components are small and decoupled.
Automate and encode: replace manual tasks with scripts or code.
Containerize: package processes with their dependencies making them easy to test, move and deploy.
Orchestrate: abstract away individual servers in production using off-the-shelf management and orchestration tools.
I think Cloud Native Architecture is all about reducing risks and going fast.
Code like a startup, deploy like there is no tomorrow. (Einstein or me)