Cloud Native Ecosystem 101 by Peter Rossbach

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Peter Rossbach copyright 2020 Accept the Challenge • Software is eating the world • Accelerate „Time to Market“ • Claim higher quality and security • Distribute your IT-Services everywhere • Use the cloud • Automate anything • Rearchitect your systems • Microservices/Serverless/Self Contained Systems • Domain Driven Design • Eventing and Messaging • Use inspect and adapt

Slide 3

Slide 3 text

Slide 4

Slide 4 text

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Slide 7

Slide 7 text

Peter Rossbach copyright 2020 Cloud Native  • Cloud Infrastructure are available • IaaS,PaaS,CaaS,FaaS • GKE, AKS, EKS, OKS, … • AI Systems (Kubeﬂow, Tensorﬂow,…) • Container technologie change the operating • Docker, Kubernetes, Mesos, Nomad • Change your architectures • Self Contained Systems • Microservices • Serverless (AWS Lambda, OpenFaaS, Knative, OpenWisk, …) • Event driven and message systems • Automation anything • Infrastructure as code • Build and Data-Pipelines • ChatOps or GitOps

Slide 8

Slide 8 text

Peter Rossbach copyright 2020 Infrastructure on demand Pay by use Automatic scale on use Use cloud ready services Available around the globe Use a platform add on (Facebook, Amazon, Salesforce, ..) Cloud Provider

Slide 9

Slide 9 text

Slide 10

Slide 10 text

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Peter Rossbach copyright 2020 • The network is reliable. • Latency is zero. • Bandwidth is inﬁnite. • The network is secure. • Topology doesn't change. • There is one administrator. • Transport cost is zero. • The network is homogeneous. The eight fallacies of distributed computing https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing

Slide 15

Slide 15 text

Slide 16

Slide 16 text

Slide 17

Slide 17 text

Slide 18

Slide 18 text

Slide 19

Slide 19 text

Slide 20

Slide 20 text

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Peter Rossbach copyright 2020 Resiliency for inter-service communications Circuit-breaking, retries and timeouts,  fault injection, fault handling, load balancing and failover. Service Discovery Discovery of service endpoints through a dedicated service registry. Routing Primitive routing capabilities, but no routing logics related  to the business functionality of the service. Observability Metrics, monitoring, distributed logging, distributed tracing. Security Transport level security (TLS) and key management. Access Control Simple blacklist and whitelist based access control. Deployment Native support for containers. Docker and Kubernetes. Interservice communication protocols HTTP1.x, HTTP2, gRPC Service Mesh

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

Slide 28

Slide 28 text

Slide 29

Slide 29 text

Slide 30

Slide 30 text

Slide 31

Slide 31 text

Slide 32

Slide 32 text

Slide 33

Slide 33 text

Slide 34

Slide 34 text

Slide 35

Slide 35 text

Peter Rossbach copyright 2020 • Build real customer systems • Starts simple and then add more complex parts • Train your people every day • Start a learning culture • Use Agile and DevOps principles and practices • Automate anything • Meet people and ask for real experiences • organize meetups • read developer blogs and tweets • visit conferences & workshops • organize company FedEX Day’s • use software craftsmanship practices • use, create and contribute to OpenSource projects Learning & Culture

Slide 36

Slide 36 text

Slide 37

Slide 37 text