with & without computers, writing Software, ~ 20 yrs ▸ Co-Lead of JUG DA (https://www.jug-da.de / @JUG_DA) ▸ Speaker at international Tech Conferences ▸ Author of „Serverless Computing in AWS Cloud“ serverlessbuch.de ▸ Twitter: @dasniko CONTAINERS VS. SERVERLESS
TO KUBERNETES ON TOP OF DC/OS MANAGED BY MESOS INSTALLED ON V I R T U A L M A C H I N E S C O N T R O L L E D B Y A HYPERVISOR RUNNING ON BARE METAL. Photo by Michael Johansson (http://www.michaeljohansson.com) …and I’m sure, I forgot a few layers!
etc) is packaged in its own container. This facilitates reproducability, transparency and resource isolation. ▸ Dynamically orchestrated Containers are actively scheduled and managed to optimize resource utilization. ▸ Microservices oriented Applications are segmented into microservices. This signiﬁcantly increases the overall agility and maintainability of applications. ▸ …and there’s also a Serverless-WG in CNCF, which has released version 0.1 of CloudEvents (cloudevents.io)! CONTAINERS VS. SERVERLESS https://www.cncf.io/about/faq/
▸ Vendor-agnostic ▸ Easier migration path ▸ Portability DISADVANTAGES OF CONTAINERS ▸ Administrative Work (e.g. apply security ﬁxes for containers, etc.) ▸ Scaling is slower ▸ Running costs ▸ Hard to get started ▸ More manual intervention see also: https://serverless.com/blog/serverless-faas-vs-containers/
Pay-per-execution ▸ Zero cost for idle time ▸ Auto-scaling ▸ Faster time-to-market ▸ Microservice nature -> clearer codebase separation ▸ Signiﬁcantly reduced administration and maintenance burden DISADVANTAGES OF SERVERLESS ▸ No standardization (yet… -> CloudEvents) ▸ „Black box“ environment ▸ Vendor lock-in (yet…) ▸ Cold starts (yet…) ▸ Complex apps can be hard to build and manage see also: https://serverless.com/blog/serverless-faas-vs-containers/