Docker Meetup Edinburgh

Serverless computing is most likely going to be the infrastructure ROI king of 2018. It would be wise for any business looking to scale to take a hard look at it. So… what the hell is serverless computing?

How can you not have servers?

It seems a bit counter-intuitive to think that the future of cloud computing and scale is a concept that sounds like philosophical bullshit. “Who needs servers, man…?” But its actually quite serious. Let’s clear the air on the most irritating aspect of serverless; serverless computing still requires servers, so the name is totally misleading. The difference between traditional cloud computing and serverless is that you, the customer who requires the computing, doesn’t pay for underutilized resources. Instead of spinning up a server in AWS for example, you’re just spinning up some code execution time. The serverless computing service takes your functions as input, performs logic, returns your output, and then shuts down. You are only billed for the resources used during the execution of those functions. Function as a Service (FaaS) Platforms

Serverless computing should really be called function-as-a-service platform. If you’ve heard about AWS Lambda or Google Cloud Function, then you’ve heard about FaaS. The benefits of these platforms is that developers don’t have to think about multi-threading or load-balancing. They can just focus on their code. They trust the FaaS to handle all the resource management for them. It also turns out to be a lot cheaper than being billed for a fixed quantity of servers. There are some downsides to using FaaS from cloud companies as well. For one, they will spin down your runtime environments if you’re not using it a lot. Paradoxically, they also limit the total amount of resources available to you, introducing latency and problems with high-performance. Monitoring, debugging, and security are also tricky with these cloud providers (as they would be with any cloud computing workflow) due to the fact that it…well… runs in a public cloud that you don’t have access to or control of.

etc.

Read the rest at Hackernoon

Why I love containderd … and Docker

Phil Estes, @estesp, IBM

Make it boring!

The goal of standardising containers is ultimately,to make them boring - Jonathan Boulle

An ode to boring: Creating Open and Stable Container world - Bob Wise (Medium)

Lets make containers boring - Vincent Bats (Red Hat)

But many platform builders and operators are looking for “boring infrastructure": a basic component that provides the robust primitives for running containers on their systems, bundled in a stable interface, and nothiing else. - Docker Blog, containerd announcement

Thanks

@estesp
github.com/estesp
estesp@gmail.com
Website: integratedcode.us
Why I love containerd…and Docker!
IRC: estesp

Container Runtimes, draw some lines

Container Runtimes, a history

LXC

systemd-nspawn

Docker

OCI Specification

Container Runtime Interface

Kubernetes

cri-o (originally oci-d)

OCI Runtimes

openconatainers/runc

oracle/railcar

kata-containers (formerly clear containers and hyperV)

nabla-containers (IBM research)

google/gvisor (runsc)

windows/hcsshim (runhcs)

systemd-nspawn native support (pr9762)

Non-Docker options

OpenFaaS with Istio

What the hell does serverless mean?

How can you not have servers?

Why I love containderd … and Docker

Thanks

google/gvisor (`runsc`)

windows/hcsshim (`runhcs`)