xRegistry v1.0-rc4 was just released! This is the last planned release before v1.0 !!! We'd love to get feedback from the community. See the release here: https://t.co/63yQIXZlKo
xRegistry spec release v1.0-rc3 is available! All major features are in and now time for final review/clean-up! Next up v1.0!!! Check it out here: https://t.co/sEbaPzFekT
. @xRegistryIO is getting traction even before we've reached v1.0. Come check us out! https://t.co/FhZpqdCfyJ
Thanks @boyney123 !
https://t.co/Kn0Uz8o7p0
xRegistry released v1.0-rc1 !
One step closer to v1.0 !
Now would be a great time to check-out the spec and make some suggestions before it gets locked down for v1.0 !
https://t.co/FhZpqdCNoh
@m_azarboon@CloudEventsIO@CloudNativeFdn@Azure There's reason to use it for internal events too, I just don't feel strongly about it.
CloudEvents spec defines useful common fields, but you're gonna end up with mostly custom fields. And you likely need org-specific tooling (shared libs, etc.) anyway.
Dispatching webhooks and events in PHp is easy enough right? But getting them structured properly?
This is why I like @CloudEventsIO , a simple structured approach to describing the events you want to throw out there.
https://t.co/0j9cZ2qIiP
Upgraded article and project to Spring Boot 3.4.0 🚀
How to Route CloudEvents messages with Spring Cloud Stream? 🤔
@CloudEventsIO#Java#SpringBoot#SpringCloud#ApacheKafka
https://t.co/8A3W0iyqxg
https://t.co/KnuBRAqeCr
The CloudEvents community is excited to announce the the CloudEvents SQL specification has reached version 1! This is the culmination of 3 years of work in the community, and we are excited to see how you use it!
More info: https://t.co/wu4zXPEdCQ
Great to present at Software Design & Dev Conf (@sddconf) in London 🇬🇧 today on open tech @CloudEventsIO and @AsyncAPISpec and how they help to document event-driven architectures such as @googlecloud pub/sub.
Slides: https://t.co/3BcuMtnKc6