Discovering Cloud Events with Cloud Run

Done at GDG Cloud Nantes: https://gdg.community.dev/events/details/google-gdg-cloud-nantes-presents-decouvrir-les-cloud-events-avec-cloud-run-cloud-run-week/
Youtube: https://youtu.be/ginM03MEbJY
GitHub: https://github.com/jlandure/cloudevents-talks

CloudEvents est une spécification de la CNCF ayant pour objectif d’améliorer la portabilité des événements publiés sur nos systèmes Cloud voir même Multi-Cloud.

Cloud Run est un produit Serverless de la Google Cloud Platform qui supporte cette spécification. Ainsi depuis Cloud Run, nous pouvons directement écouter des événements au format CloudEvents.

Nous vous montrerons des exemples d’implémentations avec des démonstrations.

Transcript

1. Discovering CloudEvents with Cloud Run Cloud Run Week Thursday 11th March 2021
2. Eric Briand @eric_briand Google Developer Expert - Cloud CTO - Zenika Julien Landuré @jlandure Google Developer Expert - Cloud CTO Group - Zenika
3. Back to the future...
4. Serverless, just a buzzword? 🤔 https://youtu.be/P8pCWhPl9B4
5. https://github.com/cncf/wg-serverless/blob/master/whitepapers/serverless-overvie w/cncf_serverless_whitepaper_v1.0.pdf
6. Serverless computing refers to the concept of building and running applications that do not require server management. It describes a finer-grained deployment model where applications, bundled as one or more functions, are uploaded to a platform and then executed, scaled, and billed in response to the exact demand needed at the moment. Serverless definition https://github.com/cncf/wg-serverless/tree/master/whitepapers/serverless-overview
7. Serverless in 2021 https://landscape.cncf.io/serverless
8. AWS GCP
9. https://xkcd.com/927/
10. https://www.cncf.io/
12. https://github.com/cncf/wg-serverless
13. https://cloudevents.io/
14. #Microservice #Container #Event-Driven “Events are everywhere, yet event publishers tend to describe events differently.
15. • Normalizing Events Across Services & Platforms • Facilitating Integrations Across Services & Platforms • Increasing Portability of Functions-as-a-Service • Improving Development & Testing of Event-Driven/Serverless Architectures • Event Data Evolution • Normalizing Webhooks • Event Tracing / Event Correlation Disclaimer : Do not try to specify any principle of Authorization, Data Integrity and Confidentiality Value proposition https://github.com/cloudevents/spec/blob/master/primer.md
16. • Cloud Events spec version • Type • Source • ID • Subject • Time • Data Content Type • Content Encoding • <Extensions> Minimal metadata https://github.com/cloudevents/spec/blob/v1.0.1/spec.md
17. • Transport Bindings for Http, Kafka, NATS, AMQP, MQTT, Websocket NEW! • Message size of 64KB • Binary or text payload: JSON, AVRO or Protobuf • No Sensitive information in the context attributes • Domain specific event data SHOULD be encrypted Transport
18. Integrations
19. Demo 🤞
20. Google Cloud Focus
21. Cloud Functions Google Cloud Serverless compute App Engine Cloud Run
22. Eventarc A unified eventing experience
23. • More than 60 sources, based on Cloud Audit Logs How does it work?
24. “Eventarc provides an easier path to receive events. You don’t have to worry about the underlying infrastructure with Eventarc. It is a managed service with no clusters to set up or maintain. ” Mete Atamel, Developer Advocate Google Cloud January 15, 2021
25. Long-term Vision
26. Demo 🤞
27. • Open Source Standard but quite new… • CNCF healthy project: Spec (format & protocol) + SDKs + Integrations • Good idea to define connectors (source & sink) • Interoperable (supported by Knative/eventing) • Superior Dev Experience thanks to a predictable format message • Decouple apps (from infrastructure and configuration) • Discoverability of event sources Our point of view
28. • 👍 No longer lock-in with the supported trigger • 😱 No news from AWS in this project “It is very similar to AWS’s CloudWatch Events functionality” • 💪 Wide range of usage (Kafka, AMQP, Webhook) • 🤔 Future of the Working Group • 🚧 New goal: get a global vision of our event-driven system thanks to Workflow https://github.com/serverlessworkflow/specification/ Next steps
29. Thank You! Eric Briand @eric_briand Julien Landuré @jlandure