Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Cloud Native Ecosystem 101

Cloud Native Ecosystem 101

Cloud native computing allows teams to build and manage services using container architectures and stringing them together into applications, without worrying about servers at all. The ecosystem is growing fast and a lot of changes are ahead. The combination of cloud services and kubernetes as a platform are the way to go. This talk give you technical overview of currently available cloud native ecosystem and future of container based systems.


Peter Rossbach

March 18, 2020

More Decks by Peter Rossbach

Other Decks in Programming


  1. 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
  2. Peter Rossbach copyright 2020 Cloud Native
 • Cloud Infrastructure are

    available • IaaS,PaaS,CaaS,FaaS • GKE, AKS, EKS, OKS, … • AI Systems (Kubeflow, Tensorflow,…) • 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
  3. 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
  4. Peter Rossbach copyright 2020 • The network is reliable. •

    Latency is zero. • Bandwidth is infinite. • 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
  5. 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
  6. 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
  7. Peter Rossbach copyright 2020 reduce complexity start a inspect &

    adapt loop Create a system architecture without an end state
  8. Peter Rossbach copyright 2020 Let other us work harder together

    & communicode AG Peter Roßbach @PRossbach [email protected] https://communicode.de https://devops-gathering.io Contact