Welcome to IE-LAB!

Generic filters
Generic filters

Native to the cloud: You need to know 6 basic things

A brief history of the local cloud

Depending on your requirements, the native cloud could mean many different things. Ten years ago, it was created by the companies such as Netflix, they take advantage of cloud technology shift from mail-order company the world’s largest consumer-demand content delivery network one. Netflix pioneered what we call the cloud-native, remodeling, expansion, and transformation of the way we all want to carry out software development.

With the huge success of Netflix and its ability to provide more functionality to customers more quickly, the company wanted to know how they implement native cloud technology to get such a huge competitive advantage.

Essentially, the term cloud is a method for improving the native service speed, but also a method of constructing a team may be utilized and scalability Kubernetes automation and containers native cloud technology offers.

Cloud native architecture: What does it look like?

Monolith and microservices Architecture

the former Netflix cloud architect Adrian Cockcroft will transfer their entire infrastructure from the overall architecture to the micro-service.

Monolithic architecture problem is that, in the development and testing of new features, these changes deployed into production takes considerable effort:

  • Require multiple teams to coordinate their code changes.
  • Once deploy multiple functions requires a lot of upfront integration and functional testing.
  • Development teams use only one or two languages.

The transition to the Netflix service micro developers to more quickly deliver new features to customers.

Micro-services leads to loosely coupled with bounded context, service-oriented architecture. This means that if each service must be updated at the same time, then it will not be “loosely coupled”; Similarly, if you must know too much around the service, then you do not “bounded background.”

Microservice, Docker, and Kubernetes

Docker container is ideal for micro-services. By running a separate container micro-service, if you prefer, they can be deployed independently, or even use a different language deployment. Containerized eliminates any risk of friction or conflict between languages, libraries or frameworks. Since the container is portable and can be operated in isolation from each other, and therefore use of the container and create a widget service architecture needed to move them to another environment it is very simple.

Container arrangement

Once you have a large number of micro-services run Docker container, you need a way to manage or arrange these containers, so that they make sense as an application. This is what you need or like Kubernetes Docker Swarm or anyone else coordinator (cluster manager) in place.

At some time in the past, you must wisely choose which orchestrator, but now the orchestra has achieved victory in the war, while Google’s Kubernetes is among the best. All major cloud providers to support Kubernetes through easy to install solution.

The point of this discussion is that most companies in order to make competitive, they must build applications around the micro-services and run them Kubernetes cluster – although some companies are run Docker containers on the other coordinator.


With the application running in the container and coordination Kubernetes, the next step is automatically deployed. Constantly automated functional flow is the difference with other DevOps philosophy and practice of software development, such as the waterfall model, where development follows an ordered sequence of phases.

Continuous does not mean that engineers 24 hours 7 days a week to update the code every day, or every time you change a line of code will deploy updates. In this sense, it refers to the continuity of continuous integration and continuous deployment of software changes and new features in the pipeline (CICD) regularly launched through automation.

Allowable Construction of continuous delivery pipeline DevOps find strategies for building more pipelines CICD.


Use containers and micro service monitoring solution must manage ever more services and servers ratio. Not only need to manage more objects, and native cloud application also generates a large amount of additional data needs to be tracked.

Collecting data from the environment so much by the moving components of a complex. Prometheus is these dynamic cloud environment The best modern solutions. It is dedicated to the application and micro-scale monitoring service running in the container, and the container is the native environments.

Cultural Change

Native implementation of cloud technology in your organization and DevOps Best Practices success depends largely on your existing corporate culture. Internal team not only learn to use cross-functional approach to ensure iterative software in a continuous rhythm, but also complement the company’s business objectives. The actual switch to cloud your native may be the easiest part of the journey; to make these changes persist and spread them throughout the organization may be the most difficult part of the process.

For more articles you can follow us on:

error: Content is protected !!
× How can I help you?