#cloudevents — Public Fediverse posts

Decision tables are good at deciding. They are terrible at waiting.

I wrote a Quarkus Flow 0.11 tutorial that keeps refund policy in plain Java and lets the workflow handle CloudEvents, correlation, manual-review callbacks, and persisted waiting state around the awkward "ask a human" path. https://www.the-main-thread.com/p/quarkus-flow-0-11-workflows-not-rules #Java #Quarkus #QuarkusFlow #CloudEvents #WorkflowEngines

Decision tables are good at deciding. They are terrible at waiting.

I wrote a Quarkus Flow 0.11 tutorial that keeps refund policy in plain Java and lets the workflow handle CloudEvents, correlation, manual-review callbacks, and persisted waiting state around the awkward "ask a human" path. https://www.the-main-thread.com/p/quarkus-flow-0-11-workflows-not-rules #Java #Quarkus #QuarkusFlow #CloudEvents #WorkflowEngines

🧩 Deel 3 (slot) van onze AsyncAPI-reeks is live.

AsyncAPI beschrijft wat er over de lijn gaat en waar. CloudEvents vult aan met hoe: een uniforme envelop met metadata (type, bron, id, timestamp).

Samen zijn ze een gelaagd model waar je makkelijk op ontwikkelt én implementeert. Handig bij notificaties, cross-team integraties en auditing.

Meedenken? [email protected]

🔗 https://developer.overheid.nl/blog/2026/06/30/asyncapi-3-implementatie-met-cloudevents

#AsyncAPI #CloudEvents #EDA

🧩 Deel 3 (slot) van onze AsyncAPI-reeks is live.

AsyncAPI beschrijft wat er over de lijn gaat en waar. CloudEvents vult aan met hoe: een uniforme envelop met metadata (type, bron, id, timestamp).

Samen zijn ze een gelaagd model waar je makkelijk op ontwikkelt én implementeert. Handig bij notificaties, cross-team integraties en auditing.

Meedenken? [email protected]

🔗 https://developer.overheid.nl/blog/2026/06/30/asyncapi-3-implementatie-met-cloudevents

#AsyncAPI #CloudEvents #EDA

Funqy gets more useful once you stop treating Knative as the first step.

This walkthrough keeps Quarkus on `localhost`, calls a function with plain HTTP, then switches to binary and structured CloudEvents to prove the contract before any broker wiring.

https://www.the-main-thread.com/p/quarkus-funqy-cloud-events-localhost

#Quarkus #CloudEvents #Knative #Java

Funqy gets more useful once you stop treating Knative as the first step.

This walkthrough keeps Quarkus on `localhost`, calls a function with plain HTTP, then switches to binary and structured CloudEvents to prove the contract before any broker wiring.

https://www.the-main-thread.com/p/quarkus-funqy-cloud-events-localhost

#Quarkus #CloudEvents #Knative #Java

3 standaarden datadeling verplicht voor de overheid

Het afgelopen half jaar zijn 3 standaarden verplicht gesteld binnen de overheid en opgenomen in de ‘pas toe leg uit-lijst’ van Forum Standaardisatie: NL-SBB, NL GOV CloudEvents en FSC (Federatieve Service Connectiviteit). Met deze stap is de Generieke Digitale Infrastructuur (GDI) weer wat rijker, en dat helpt overheden bij het inrichten van hun digitale dienstverlening.

De standaarden zijn ook van belang voor het Federatief Datastelsel (FDS). Dit stelsel helpt overheden om gegevens eenvoudig, transparant, veilig en vertrouwd met elkaar te delen. Overheidsorganisaties wisselen steeds meer gegevens met elkaar uit. Dat is nodig om aan maatschappelijke opgaven te werken en proactieve dienstverlening te kunnen bieden aan burgers en bedrijven. Dat vraagt om duidelijke afspraken en technische standaarden.

Elke standaard een eigen functie

De 3 standaarden ondersteunen verschillende onderdelen van datadeling:

• NL-SBB helpt organisaties om de begrippen in datasets op een uniforme manier te beschrijven en vindbaar te maken.
• NL GOV CloudEvents maakt het mogelijk om systemen automatisch te informeren wanneer iets in de dataset verandert of wanneer een gebeurtenis plaatsvindt.
• FSC uniformeert de koppelingen tussen organisaties, zodat de datadeling beheersbaar, transparant, veilig en herleidbaar georganiseerd is.

Gezamenlijke basis voor datadeling

Door deze standaarden op te nemen in de GDI en de ‘pas toe of leg uit-status’ te geven, ontstaat meer duidelijkheid en richting, en kunnen overheidsorganisaties na adoptie van de standaarden beter op elkaar aansluiten. Organisaties die data delen of systemen op elkaar aansluiten, passen deze standaarden toe. Zo groeit stap voor stap een gezamenlijke basis voor datadeling binnen het Federatief Datastelsel, in lijn met de NDS-prioriteit Data.

Lees het nieuwsbericht op de website van Realisatie IBDS.

Dit is een automatisch geplaatst bericht. Vragen of opmerkingen kun je richten aan @[email protected]

#CloudEvents #datadeling #FDS #FederatiefDatastelsel #FSC #gegevensuitwisseling #IBDS #InterbestuurlijkeDatastrategie #nieuwsbrief52026 #NLSBB #Standaarden

3 standaarden datadeling verplicht voor de overheid

Het afgelopen half jaar zijn 3 standaarden verplicht gesteld binnen de overheid en opgenomen in de ‘pas toe leg uit-lijst’ van Forum Standaardisatie: NL-SBB, NL GOV CloudEvents en FSC (Federatieve Service Connectiviteit). Met deze stap is de Generieke Digitale Infrastructuur (GDI) weer wat rijker, en dat helpt overheden bij het inrichten van hun digitale dienstverlening.

De standaarden zijn ook van belang voor het Federatief Datastelsel (FDS). Dit stelsel helpt overheden om gegevens eenvoudig, transparant, veilig en vertrouwd met elkaar te delen. Overheidsorganisaties wisselen steeds meer gegevens met elkaar uit. Dat is nodig om aan maatschappelijke opgaven te werken en proactieve dienstverlening te kunnen bieden aan burgers en bedrijven. Dat vraagt om duidelijke afspraken en technische standaarden.

Elke standaard een eigen functie

De 3 standaarden ondersteunen verschillende onderdelen van datadeling:

• NL-SBB helpt organisaties om de begrippen in datasets op een uniforme manier te beschrijven en vindbaar te maken.
• NL GOV CloudEvents maakt het mogelijk om systemen automatisch te informeren wanneer iets in de dataset verandert of wanneer een gebeurtenis plaatsvindt.
• FSC uniformeert de koppelingen tussen organisaties, zodat de datadeling beheersbaar, transparant, veilig en herleidbaar georganiseerd is.

Gezamenlijke basis voor datadeling

Door deze standaarden op te nemen in de GDI en de ‘pas toe of leg uit-status’ te geven, ontstaat meer duidelijkheid en richting, en kunnen overheidsorganisaties na adoptie van de standaarden beter op elkaar aansluiten. Organisaties die data delen of systemen op elkaar aansluiten, passen deze standaarden toe. Zo groeit stap voor stap een gezamenlijke basis voor datadeling binnen het Federatief Datastelsel, in lijn met de NDS-prioriteit Data.

Lees het nieuwsbericht op de website van Realisatie IBDS.

Dit is een automatisch geplaatst bericht. Vragen of opmerkingen kun je richten aan @[email protected]

#CloudEvents #datadeling #FDS #FederatiefDatastelsel #FSC #gegevensuitwisseling #IBDS #InterbestuurlijkeDatastrategie #nieuwsbrief52026 #NLSBB #Standaarden

@virtualpierogi @sri @jsalvador @ben @nlnet

When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.

If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.

And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.

@virtualpierogi @sri @jsalvador @ben @nlnet

When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.

If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.

And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.

Streamifying Reference Data for Temporal Consistency with Telemetry Events #cloudevents #dataengineering

https://vasters.com/clemens/2024/10/30/streamifying-reference-data-for-temporal-consistency-with-telemetry-events

Streamifying Reference Data for Temporal Consistency with Telemetry Events #cloudevents #dataengineering

https://vasters.com/clemens/2024/10/30/streamifying-reference-data-for-temporal-consistency-with-telemetry-events

One session at #synyxCamp discussed the latest @thoughtworks tech radar. I was surprised to see #Cloudevents on "adopt".

I get that a standard like this can be beneficial but is it really a game changer? What is your experience with it? And where should it be used?

https://cloudevents.io/

#Softwarearchitecture #eventdriven #coding

One session at #synyxCamp discussed the latest @thoughtworks tech radar. I was surprised to see #Cloudevents on "adopt".

I get that a standard like this can be beneficial but is it really a game changer? What is your experience with it? And where should it be used?

https://cloudevents.io/

#Softwarearchitecture #eventdriven #coding

#CloudEvents open specification has reached graduation at the #CNCF 👏
The spec has been adopted by #Adobe I/O Events, #AlibabaCloud EventBridge, #Azure Event Grid, #GoogleCloud Eventarc, #IBMCloud Code Engine, the European Commission and more.
And of course it's been adopted by CNCF projects, such as #Argo, #Falco, #Harbor, and #Knative.
The beauty is that it fits in nicely with existing eventing infrastructure, so I expect more adopters to follow
https://www.cncf.io/announcements/2024/01/25/cloud-native-computing-foundation-announces-the-graduation-of-cloudevents/
#opensource #cloudnative

#CloudEvents open specification has reached graduation at the #CNCF 👏
The spec has been adopted by #Adobe I/O Events, #AlibabaCloud EventBridge, #Azure Event Grid, #GoogleCloud Eventarc, #IBMCloud Code Engine, the European Commission and more.
And of course it's been adopted by CNCF projects, such as #Argo, #Falco, #Harbor, and #Knative.
The beauty is that it fits in nicely with existing eventing infrastructure, so I expect more adopters to follow
https://www.cncf.io/announcements/2024/01/25/cloud-native-computing-foundation-announces-the-graduation-of-cloudevents/
#opensource #cloudnative

The latest @thoughtworks #TechRadar (https://www.thoughtworks.com/radar) is thin on data-related entries this time around (and heavy on the AI-related stuff, unsurprisingly). A few that caught my eye

🟢Adopt: #dbt https://www.thoughtworks.com/radar/tools/summary/dbt

🟢Trial #CloudEvents https://www.thoughtworks.com/radar/platforms/summary/cloudevents

🟢Trial #TrinoDB https://www.thoughtworks.com/radar/platforms/summary/trino

🟢Assess: #pgvector https://www.thoughtworks.com/radar/platforms/summary/pgvector

🟢Trial: #polars https://www.thoughtworks.com/radar/languages-and-frameworks/summary/polars

Full @thoughtworks #TechRadar here: https://www.thoughtworks.com/radar

The latest @thoughtworks #TechRadar (https://www.thoughtworks.com/radar) is thin on data-related entries this time around (and heavy on the AI-related stuff, unsurprisingly). A few that caught my eye

🟢Adopt: #dbt https://www.thoughtworks.com/radar/tools/summary/dbt

🟢Trial #CloudEvents https://www.thoughtworks.com/radar/platforms/summary/cloudevents

🟢Trial #TrinoDB https://www.thoughtworks.com/radar/platforms/summary/trino

🟢Assess: #pgvector https://www.thoughtworks.com/radar/platforms/summary/pgvector

🟢Trial: #polars https://www.thoughtworks.com/radar/languages-and-frameworks/summary/polars

Full @thoughtworks #TechRadar here: https://www.thoughtworks.com/radar

An intro to #CloudEvents by @atamel with lots of interesting pointers and references:

https://atamel.dev/posts/2023/04-03_cloudevents_basics/

An intro to #CloudEvents by @atamel with lots of interesting pointers and references:

https://atamel.dev/posts/2023/04-03_cloudevents_basics/

@jonskeet didn't know you are working for #CloudEvents but you answered my question about #knative functions in 5 minutes.
Slightly off topic, so not about functions but just about knative eventing and serving:
what about #dotnet (c#) cold startup times for serverless pods scaling to zero?
Is that a resolved issue nowadays?

@jonskeet didn't know you are working for #CloudEvents but you answered my question about #knative functions in 5 minutes.
Slightly off topic, so not about functions but just about knative eventing and serving:
what about #dotnet (c#) cold startup times for serverless pods scaling to zero?
Is that a resolved issue nowadays?

My review of 5 leading open source standards: OpenTelemetry, OpenFeature, CloudEvents, CDEvents and the Open Cybersecurity Framework (OCSF).

https://youtu.be/D6KqtJIVcts
#opentelemetry #openfeature #cloudevents #cdfoundation #cdevents and #ocsf

My review of 5 leading open source standards: OpenTelemetry, OpenFeature, CloudEvents, CDEvents and the Open Cybersecurity Framework (OCSF).

https://youtu.be/D6KqtJIVcts
#opentelemetry #openfeature #cloudevents #cdfoundation #cdevents and #ocsf

Before I vanish into the Karneval festivities for the next several days:

The #CloudEvents "Discovery" sub-working group has spent a ton of time last year to build a set of specs to describe metadata for eventing/messaging systems. The specs are not done, but getting close. 🧵

Before I vanish into the Karneval festivities for the next several days:

The #CloudEvents "Discovery" sub-working group has spent a ton of time last year to build a set of specs to describe metadata for eventing/messaging systems. The specs are not done, but getting close. 🧵

Storing #CloudEvents in #PostgreSQL using jsonb:

https://blog.kie.org/2023/02/cloudevents-labeling-and-classification-with-drools.html

As in, you can use a regular database for your cloud events!

Storing #CloudEvents in #PostgreSQL using jsonb:

https://blog.kie.org/2023/02/cloudevents-labeling-and-classification-with-drools.html

As in, you can use a regular database for your cloud events!

Issues have been raised and PRs submitted to add end-to-end message security metadata (borrowed from JOSE/JWE) to #CNCF #CloudEvents.

In today's WG meeting, I pointed out that some folks there (&me) still have deep scars from WS-Security and that we should definitely stay at least one spec away from keys and algos.

A CloudEvent can be mapped to an HTTP message, which is an Internet message, w/ which S/MIME can be used. Then we have an E2E message and avoided inventing something.

#infosec

Issues have been raised and PRs submitted to add end-to-end message security metadata (borrowed from JOSE/JWE) to #CNCF #CloudEvents.

In today's WG meeting, I pointed out that some folks there (&me) still have deep scars from WS-Security and that we should definitely stay at least one spec away from keys and algos.

A CloudEvent can be mapped to an HTTP message, which is an Internet message, w/ which S/MIME can be used. Then we have an E2E message and avoided inventing something.

#infosec

Messaging & Eventing resources https://github.com/clemensv/messaging #mqtt #amqp #CloudEvents #Azure

Proper #introduction

I'm a software architect working for #microsoft on the #Azure cloud's messaging services and help developing several open standards, including @[email protected] #CloudEvents.

I also like taking #photos of all sorts of things, I'm a football/soccer supporter of # borussia Mönchengladbach, drive an #ev I charge with solar power, and I may know more about airplanes than needed. #avgeek #neuhier

Proper #introduction

I'm a software architect working for #microsoft on the #Azure cloud's messaging services and help developing several open standards, including @[email protected] #CloudEvents.

I also like taking #photos of all sorts of things, I'm a football/soccer supporter of # borussia Mönchengladbach, drive an #ev I charge with solar power, and I may know more about airplanes than needed. #avgeek #neuhier