Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The Game!

@diego_pacheco Diego Pacheco @ ilegra.com Principal Software Architect

Arquitetura mais comun no Mercado.

Datacenter mais comun no Mercado.

Dev e Ops

A era da caixa mágica…

Resultado!

Manifesto SOA

MSA veio depois de SOA

Microservices: Cases - Benchmark

~600 microservices ~150 microservices para uma página

Isolamento

Isolamento: Beneficios

Times Recursos Gestão

DevOps Engineering

Deploys Amazon 2015

Deploys Rate

Deploys Amazon 2015

Deploys: Benefits

Akka as Microservice solution

Netflix OSS - IPC

12 Factor App

http://12factor.net/

Cloud Native

Cloud Native

Stateless Services Ephemeral Instances Everything fails all the time Auto Scaling / Down Scaling Multi-Region No SPOF Design for Failure (expected)

SRE

Reliability is defined as “the probabilityof failure free software operationfor a specified period of timeIn a specified enviroment”

SRE

Anti-Fragilidade

Design for Failure Test Caos and Failures Automate as much as possible There are Tools that could help us Create Culture of Caos/Failure Testing periodically Ops Tooling / Metrics Incident Training Chaos / Failures

New Practices

Exception Handling Isolate Failure – Avoid JEE like Cascading Redundancy – NO SPOF Auto-Scaling Clusters Fault Tolerance and Isolation Fallbacks and Degraded Experience Protect Customer from failures – Don’t throw

Failures -> Failures VS Errors

Design For Failure

http://principlesofchaos.org/

https://github.com/Netflix/SimianArmy

Runtime Testing

New: DoD / Tests

https://github.com/tylertreat/Comcast

Comcast

New Rules of the Game

Microservices Cloud Native SRE/Chaos Engineering DevOps Engineering

Cloud Native, Microservices and SRE/Chaos Engineering: The new Rules of The Game!

@diego_pacheco Diego Pacheco @ ilegra.com Principal Software Architect

Obrigado!