@MIT series is a group of articles being written to describe my learning path attending to the Cloud & DevOps: Continuous Transformation at the MIT.

This article at a glance — TL;DR

The Cloud Native foundation as a good source to check new moves from the cloud industry

The content

Cloud-Native Computing Foundation: For an application to be considered truly Cloud Native they need to be:

  1. Built for fault tolerance
  2. Horzontally scalable
  3. Written in a manner that takes full advantage of what cloud providers have to offer.

Cloud Native Applications prioritize the following:

  1. Speed
  2. Short cycles
  3. Microservices
  4. Loosely coupled
  5. DevOps

Pet vs cattle way of handling our servers:

As a developer, you care about the application being hand-cared for − when it is sick, you care of it, and if it dies, then it is not easy to replace. It’s like when you name a pet and take care of it; if one day it is missing, everyone will notice. In the case of cattle, however, you expect that there will always be sick and dead cows as part of daily business; in response, you build redundancies and fault tolerance into the system so that ‘sick cows’ do not affect your business. Basically, each server is identical and if you need more, you create more so that if any particular one becomes unavailable, no one will notice.

Cloud native action spectrum:

Cloud native roadmap of adoption (the majority of companies are on step 4):

There’s a landscape map listing tons of vendors on the cloud native foundation for each specific need: http://landscape.cncf.io

Exercises and Assignments

  • Assignment: Create a presentation showing the push you are planning for your company. Think about steps, risks, mitigations, and how you plan to lead the journey. Think about the presentation as if you were presenting it to your CEO or a client.

Sharing experiences on IT subjects. Working for AWS. DevOps, Kubernetes, Microservices, Terraform, Ansible, and Java