The CNCF point of view on Serverless
Presentation at Serverlessconf NYC on October 11, 2017.
https://nyc.serverlessconf.io/
The CNCF Serverless Working Group - with participation from IBM, AWS, Google, Huawei, Red Hat, VMware and many others - has been working on guidance to help end developers understand serverless computing. relative to other cloud-native deployment options such as container orchestration (for example, Kubernetes) and Platform-as-a-Service (for example, Cloud Foundry and OpenShift). A soon-to-be-published whitepaper aims to educate users about the right workloads for serverless, help them make sense of the landscape of service providers, and recommend open source projects for inclusion in the CNCF. In this lightning talk you'll hear about our work and learn how you can help steer serverless adoption and project support from the CNCF.
Serverless architectures are rapidly gaining interest from developers but it can be hard to understand when a serverless platform makes the most sense for their next application and how long a given provider might be around to support their apps. The CNCF aims to help users learn about serverless and support emerging open source projects that can run, debug, and monitor the next generation of cloud-native applications.
%in ivory park+277-882-255-28 abortion pills for sale in ivory park
The CNCF on Serverless
1. The CNCF on Serverless
Daniel Krook • Software Engineer • IBM
2. @DanielKrook
The CNCF supports modern distributed systems
Create and drive the adoption of a new computing
paradigm that is optimized for modern distributed
systems environments capable of scaling to tens
of thousands of self healing multi-tenant nodes.
• Provide stewardship for projects
• Foster growth and evolution of ecosystems
• Promote of the underlying technologies
• Make the technology accessible and reliable
Fast • Open • Fair
6. @DanielKrook
Four current CNCF Working Groups
Provides infrastructure to
hosted projects.
Looks to offer integration
testing between projects.
Providing a Container
Networking Interface
(CNI) specification.
Aims for connectivity and
portability in cloud native
application networking.
Providing a Container
Storage Interface (CSI)
specification.
Aims for portability
across cloud
orchestration systems.
Educate cloud native
developers on serverless
architectures.
Determine what the
CNCF should do in this
space.
Recommend involvement
in specifications and
projects.
7. @DanielKrook
CNCF Serverless Working Group
Formed in June 2017
Participation from:
Google, Red Hat, Huawei, IBM, Microsoft,
SolarWinds, Docker, iguazio, Amazon,
MasterCard, Pivotal, VMware, Serverless
Inc., Clay Labs, The New Stack, A Cloud
Guru, Platform9, Bitnami, Auth0, and Hyper.
github.com/cncf/wg-serverless
8. @DanielKrook
CNCF Serverless Working Group
● Describes serverless platforms as they exist today using a common vocabulary.
● Highlights promising use cases and areas where they’ve already proven value.
● Differentiates serverless from PaaS and Container Orchestration.
● Describes the mechanics of a generic serverless system.
github.com/cncf/wg-serverless
9. @DanielKrook
CNCF Serverless Working Group
Creating a common model for event data, similar to CNI and CSI.
Coalescing on a single format between a few proposals:
● Cloud-Native Event Mapping (CNEM) – (iguazio)
● OpenEvents – (Serverless, Inc.)
● Cloud Auditing Data Federation – (IBM, DMTF)
Handle
any event
from
anywhere
github.com/cncf/wg-serverless
10. @DanielKrook
CNCF Serverless Working Group
● Maintain a matrix and landscape of serverless implementations and features.
● Produce additional documents and samples that educate users on serverless apps.
● Document integration with other CNCF projects, such as how to monitor and observe.
● Potential collaboration on a declarative packaging format specification.
github.com/cncf/wg-serverless