Why?

Events are everywhere. However, event publishers tend to describe events differently.

  • Consistency

    The lack of a common way of describing events means developers must constantly re-learn how to receive events.

  • Accessibility

    This also limits the potential for libraries, tooling and infrastructure to aide the delivery of event data across environments, like SDKs, event routers or tracing systems.

  • Portability

    The portability and productivity we can achieve from event data is hindered overall.

What?

Enter CloudEvents, a specification for describing event data in a common way. CloudEvents seeks to ease event declaration and delivery across services, platforms and beyond!

CloudEvents is a new effort and it’s still under active development. However, its working group has received a surprising amount of industry interest, ranging from major cloud providers to popular SaaS companies. Our end goal is to offer this specification to the Cloud Native Computing Foundation.

Contribute!

This effort is organized via the CNCF’s Serverless Working Group and everyone is encouraged to join us. If you’re interested in contributing, please collaborate with us in the CloudEvents Github Org, join our weekly call every Thursday at 9AM PT via Zoom, and review our Governance model to familiarize yourself with our process.

v1.0 Announcement!

CloudEvents 1.0 Release

On October 24, 2019 the CloudEvents project had two significant achievements. First, the CNCF’s Technical Oversight Committee approved the project as an “incubator” project, graduating from “sandbox”. Second, the CloudEvents specification released version 1.0 of its deliverables!

This is the first major release of the specification and represents two year’s worth of hard work by a truly great team of people from across the entire serverless community. We’ve had just about every major cloud provider participate, several “end-user” companies as well as many individual participants all working diligently on producing a specification that will hopefully continue to see increased adoption now that this milestone has been reached.

Aside from the core CloudEvents specification, there’s also the Primer and protocol and format specifications (all of which can be found on the github repo. Additionally, there are 5 different SDKs to help people produce and consume CloudEvents.

The CNCF Serverless Working Group will be deciding what to focus on next (e.g. additional CloudEvents related activities, or perhaps address some other interoperability pain-point the community is experiencing). So, if you’re interested please join the regular weekly calls. Additionally, there is the work being done on the workflow specification.

Thanks and congratulations to everyone who participated in this work!