Cloud Native: The Cattle, the Pets, and the Germs, by Avishai Ish-Shalom

•

0 likes•95 views

10 years ago, we promoted the move from pet systems to faceless hordes of electronic cattle grazing on commodity infrastructure. But as the evolution of the cloud progresses we find that the cattle methodology is no longer sufficient and that cloud native systems resemble some other biological entity…

Technology

@nukemberg
Cloud native: The pets, the
cattle and the germs
Avishai Ish-Shalom (@nukemberg)

@nukemberg
“Native Cloud Application (NCA) refers to a type
of computer software that natively utilizes
services and infrastructure provided by cloud
computing providers”

@nukemberg
“scalable applications in modern, dynamic
environments such as public, private, and hybrid
clouds”

@nukemberg
“Containers, service meshes,
microservices, immutable infrastructure,
and declarative APIs exemplify this
approach.
These techniques enable loosely
coupled systems that are resilient,
manageable, and observable”

@nukemberg
Manageable through tight coupling
Tight coupling through reliability
Reliability through stable environment
Stable environment through control

@nukemberg
We lost control of the environment
● Unreliable network
● Noisy neighbours
● Flaky performance
● Servers just go away

@nukemberg
We lost statis
● Number of servers change
● IP addresses change
● Network topology changes
● Data conflicts

@nukemberg
Microservices
● Single purpose, semi autonomous
● Loosely coupled
● Blackboxes
● API

@nukemberg
root@appymuppy-23 ~$
root@i-82a4f21a ~$
root@app-server ~$
root@app-3 ~$

@nukemberg
Production change every 3 minutes (avg)
Code deployed every 7 seconds (avg)

@nukemberg
You don’t have a production environment
● Every client talks to multiple different systems
● On difference DCs/clouds
● Did I mention A/B tests?
● Or personalization?

@nukemberg
You have production environments
● Every transaction sees a unique “environment”
● One time environment
● Non repeatable

@nukemberg
The cloud is inherently public

@nukemberg
Complex dynamic system hosted in an
uncontrollable, dynamic environment

@nukemberg
“A complex adaptive system is a system in
which a perfect understanding of the individual
parts does not automatically convey a perfect
understanding of the whole system's behavior”

@nukemberg
Biological systems
● Semi autonomous cooperating cells
● Self organizing
● Adaptive
● Dynamic, constant birth/death
● Innate variation
● Surviving in an uncontrollable, sometimes hostile environment

@nukemberg
But how?
● Large number of redundant agents
● Similar, but not identical
● Short lifespan
● Autonomous
● Convergent behaviour
● Cooperation instead of imposition

@nukemberg
Computer immunology, 1998
Mark Burgess, father of Promise theory and
Configuration Management
● Macro level stability
● Convergence
● Continuous active maintenance

@nukemberg
New challenges
Observing a dynamic, information rich network
Managing numerous semi-autonomous components
Understanding a loosely coupled self organizing ensemble
Controlling a non-linear chaotic system
Security in a public, hostile environment
Macro level resilience with unique one-time topology

@nukemberg
Thank you
https://jobs.aleph.vc/

Similar to Cloud Native: The Cattle, the Pets, and the Germs, by Avishai Ish-Shalom

CrawlerLD - Distributed crawler for linked data

Raphael do Vale

Performance Testing in Production - Leveraging the Universal Scalability Law

Kevin Brockhoff

AMW43 - Unba.se, Distributed database for human interaction

Daniel Norman

Persistent object sharing for sidle services

Coders Hub

Replication in Distributed Systems

Kavya Barnadhya Hazarika

Reactive Applications in Java

Alexander Mrynskyi

sp2015ren

Danny Vo

PMSCS 657_Parallel and Distributed processing

Md. Mashiur Rahman

cf.Objective() 2017 - Design patterns - Brad Wood

Ortus Solutions, Corp

Architectural Patterns of Resilient Distributed Systems

Ines Sombra

A Python Petting Zoo

devondjones

CQRS and Event Sourcing in Action

Knoldus Inc.

The demands and expectations for applications have changed dramatically in recent years. Applications today are deployed on a wide range of infrastructure; from mobile devices up to thousands of nodes running in the cloud—all powered by multi-core processors. They need to be rich and collaborative, have a real-time feel with millisecond response time and should never stop running. Additionally, modern applications are a mashup of external services that need to be consumed and composed to provide the features at hand. We are seeing a new type of applications emerging to address these new challenges—these are being called Reactive Applications. In this talk we will discuss four key traits of Reactive; Event-Driven, Scalable, Resilient and Responsive—how they impact application design, how they interact, their supporting technologies and techniques, how to think when designing and building them—all to make it easier for you and your team to Go Reactive.

Go Reactive: Event-Driven, Scalable, Resilient & Responsive Systems

Jonas Bonér

System design fundamentals CAP.pdf

UsmanAhmed269749

Actor model in F# and Akka.NET

Riccardo Terrell

BISSA: Empowering Web gadget Communication with Tuple Spaces

Srinath Perera

Real time visualization of structured things

Nurul Amin Choudhury

Stateless service architectures can be easily scaled horizontally by adding backend servers to a front-end load balancer. Such approach is not always optimal, any application that needs to perform soft real-time work could never be built using stateless CRUD models, because state locality is required in order to achieve those response times. In this talk I'll cover benefits of statefull services, gave an overview of academic research and existing frameworks in js, scala, .net and golang worlds. Unfortunately in this area python has little to offer. To fix this we will figure out key concepts for building scalable stateful services: membership and dissemination protocols, failure detection and message routing.

KEY CONCEPTS FOR SCALABLE STATEFUL SERVICES

Mykola Novik

Presentation given by our CEO Mike Kelly at this year's Excellence in Policing conference talking about the benefits of cloud computing and the Effectiveness, Efficiency and Legitimacy of outsourcing data. The presentation looks at the long term trends supporting the adoption of cloud technologies and dispels some of the myths and reasons why not to adopt cloud. The presentation concludes with an examination of the benefits of utilising cloud technology and examines how best to adopt a cloud approach.

The Effectiveness, Efficiency and Legitimacy of Outsourcing Your Data

DataCentred

Agent Based Modeling and Simulation - Overview and Tools

Stathis Grigoropoulos

Similar to Cloud Native: The Cattle, the Pets, and the Germs, by Avishai Ish-Shalom (20)

CrawlerLD - Distributed crawler for linked data

Performance Testing in Production - Leveraging the Universal Scalability Law

AMW43 - Unba.se, Distributed database for human interaction

Persistent object sharing for sidle services

Replication in Distributed Systems

Reactive Applications in Java

sp2015ren

PMSCS 657_Parallel and Distributed processing

cf.Objective() 2017 - Design patterns - Brad Wood

Architectural Patterns of Resilient Distributed Systems

A Python Petting Zoo

CQRS and Event Sourcing in Action

Go Reactive: Event-Driven, Scalable, Resilient & Responsive Systems

System design fundamentals CAP.pdf

Actor model in F# and Akka.NET

BISSA: Empowering Web gadget Communication with Tuple Spaces

Real time visualization of structured things

KEY CONCEPTS FOR SCALABLE STATEFUL SERVICES

The Effectiveness, Efficiency and Legitimacy of Outsourcing Your Data

Agent Based Modeling and Simulation - Overview and Tools

More from Cloud Native Day Tel Aviv

Cloud Native is a Cultural Decision. By Reshef Mann

Cloud Native Day Tel Aviv

In any Cloud Native architecture there’s a seemingly endless stream of events that happen at each layer. These events can be used to detect abnormal activity and possible security incidents, as well as providing an audit trail of activity. In this talk we’ll cover how we extended Falco to ingest events beyond just host system calls, such as Kubernetes audit events or even application level events. We will also show how to create Falco rules to detect behaviors in these new event streams. We show how we implemented Kubernetes audit events in Falco, and how to configure the event stream.

Container Runtime Security with Falco, by Néstor Salceda

Cloud Native Day Tel Aviv

Kafka Mirror Tester: Go and Kubernetes Powered Test Suite for Kafka Replicati...

Cloud Native Day Tel Aviv

Running I/O intensive workloads on Kubernetes, by Nati Shalom

Cloud Native Day Tel Aviv

Service meshes are all the buzz in cloud-native world. How come only yesterday we didn't know such a thing existed and now everybody seems to want one? If you're already running a microservice-based system or only starting out with one, you may be asking yourself : "Do I also need a mesh?" In this session we'll try to answer what the mesh is good for, what problem it solves, what new questions it poses.

WTF Do We Need a Service Mesh? By Anton Weiss.

Cloud Native Day Tel Aviv

Update Strategies for the Edge, by Kat Cosgrove

Cloud Native Day Tel Aviv

Building a Cloud-Native SaaS Product The Hard Way. By Arthur Berezin

Cloud Native Day Tel Aviv

If you are interested in monitoring, and successfully set up a system (whether home-grown or custom-off-the-shelf) for your own use, there comes a moment when you go from monitoring only the systems you care about, to monitoring systems that other people care about. Monitoring for yourself is all about having the best data for the least effort. Monitoring for others? That's when your job becomes a game of "what just happened" whack-a-mole.

The Four Questions (Every Monitoring Engineer gets asked), by Leon Adato

Cloud Native Day Tel Aviv

K8s Pod Scheduling - Deep Dive. By Tsahi Duek.

Cloud Native Day Tel Aviv

MySQL shell is the MySQL client of the future. It will help you in your daily operations, whatever they are. It doesn't matter if you are a developer or an administrator, if you want to work with relational or non relational data, if you want to setup or monitor your cluster, if you want to work with SQL language or javascript or python. Discover how MySQL shell will help you, no matter what you want to do with MySQL!

MySQL Shell: the daily tool for devs and admins. By Vittorio Cioe.

Cloud Native Day Tel Aviv

Cloud native transformation patterns, by Pini Reznik

Cloud Native Day Tel Aviv

Cloud and Edge: price, performance and privacy considerations in IOT, by Tsvi...

Cloud Native Day Tel Aviv

Running Highly Available Large Scale Systems is a lot of work. For the past 2.5 years, we've been running 100% serverless on a full production environment, serving customers worldwide. No VMs, no containers, no Kubernetes. Just code. In this session I will present why we decided to go fully serverless at Torii, how it helped us move faster than our competitors, where did serverless computing worked best and where there's more work to be done.

Two Years, Zero servers: Lessons learned from running a startup 100% on Serve...

Cloud Native Day Tel Aviv

The “Twelve-Factor” application model has come to represent twelve best practices for building modern, cloud-native applications. With guidance on things like configuration, deployment, runtime, and multiple service communication, the Twelve-Factor model prescribes best practices that apply to everything from web applications to APIs to data processing applications. Although Serverless computing and AWS Lambda have changed how application development is done, the “Twelve-Factor” best practices remain relevant and applicable in a Serverless world. In this talk, we’ll apply the “Twelve-Factor” model to Serverless application development with AWS Lambda and Amazon API Gateway and show you how these services enable you to build scalable, low cost, and low administration applications.

12 Factor Serverless Applications - Mike Morain, AWS - Cloud Native Day Tel A...

Cloud Native Day Tel Aviv

When creating a new Microservice you typically need to add a lot of boilerplate to the code, such as logging, metrics, authentication, SSL, secrets/credentials, etc... All this ends up overshadowing the actual logic of the service itself and results in a lot of dependencies and code. Because of this, we at Soluto created a template for the boilerplate, which worked great... Until we had to upgrade one of the dependencies which resulted in huge effort of code upgrades and deployment across each and every service that uses the template. And that’s besides the fact we needed to make a separate template for each language we used (and over the years, the number of programming languages we use at production increased dramatically). We needed a way to simplify all this. We wanted to get rid of the boilerplate while maintaining the functions listed above. So we decided to delegate the entire responsibility to the Kubernetes infrastructure. In this lecture, I will do a live coding session and show you how to remove the boilerplate from your code and move it to the infrastructure, and discuss the benefits and limitations of this approach.

Not my problem! Delegating responsibilities to the infrastructure - Yshay Yaa...

Cloud Native Day Tel Aviv

Machine Learning is no doubt the hottest trend in IT nowadays. Deep Neural Network (DNN), a subfield of Machine Learning with mode of operation loosely inspired by the brain, allows us to solve complex problems such as image recognition that has been very difficult to solve using standard programming paradigms. DNN concepts are not new. However, and until recently, applying them in practice could not be realized due to their high computational demands. With the recent development in parallel computing, especially around GPU acceleration and high speed and efficient networking, DNN has become a reality in modern data centers. In this talk we will describe the system requirements to effectively run a machine learning cluster with popular frameworks such as TensorFlow. We will discuss how such a system can be deployed in an OpenStack-based cloud without compromises, enjoying high-performance DNN programming paradigm as well as the benefits of cloud and software-defined data centers.

Brain in the Cloud: Machine Learning on OpenStack & Kubernetes Done Right - E...

Cloud Native Day Tel Aviv

Cloud native applications are commonly thought as stateless, horizontally scalable workloads that you can scale-up and down on-demand. Kubernetes, as the commodity cloud native orchestrator, was originally designed for such workloads. A lot has evolved since Kubernetes’ inception, and nowadays many of the stateful applications are migrating to Kubernetes. While not everything is perfect, more and more features are added to support complex stateful use-cases. In this session Arthur will cover the following topics: - Breakdown of a stateful application - Planning a stateful application on Kubernetes - The state of Kubernetes StatefulSets, Persistent Volumes, DNS, Networking, operators and High Availability - A practical use-case and DEMO of a stateful application with Kubernetes

A stateful application walks into a Kubernetes bar - Arthur Berezin, JovianX ...

Cloud Native Day Tel Aviv

The story of how KubeMQ was born - Oz Golan, KubeMQ - Cloud Native Day Tel Av...

Cloud Native Day Tel Aviv

I want it all: go hybrid - Orit Yaron, Outbrain - Cloud Native Day Tel Aviv 2018

Cloud Native Day Tel Aviv

Keeping I.T. Real - Aaron Wolf, Mathematics and computer programming teacher,...

Cloud Native Day Tel Aviv

More from Cloud Native Day Tel Aviv (20)