Cloud Events

115 posts

Cloud Events

Cloud Events

@CloudEventsIO

شامل ہوئے Mayıs 2018
1 فالونگ1.1K فالوورز
Cloud Events ری ٹویٹ کیا
xRegistry
xRegistry@xRegistryIO·
xRegistry v1.0-rc2 was released today! Almost at v1.0...it'll be here very soon! Check it out! github.com/xregistry/spec
English
0
2
3
140
Richard Collette
Richard Collette@rpcollette·
@CloudEventsIO - It seems like an issue if there is one maintainer on something like the .NET SDK, and doesn't have time to manage PRs. Can you open it to more?
English
1
0
0
12
Cloud Events ری ٹویٹ کیا
xRegistry
xRegistry@xRegistryIO·
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 ! github.com/xregistry/spec
English
0
2
2
143
Cloud Events
Cloud Events@CloudEventsIO·
CloudEvent-ify all events!
Yan Cui@theburningmonk

@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.

English
0
2
5
254
Cloud Events ری ٹویٹ کیا
JustSteveKing
JustSteveKing@JustSteveKing·
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. github.com/JustSteveKing/…
English
0
4
19
1.5K
David Boyne 🚀
David Boyne 🚀@boyney123·
Hey! Ways to think about it, @CloudEventsIO for standards on your message (envelope), what goes inside is still up to you. Helps with interoperability. @AsyncAPISpec for a machine readable format for your messaging systems. Think OpenAPI but for event-driven architecture, document you messages, channels, protocols, etc. This is a great way for teams to find info they need and start to undersand your services without needing to dive into the code. What I'm trying to do with @event_catalog is provide another layer of info for your teams. Using these open source standards and specs to help them add semantic meaning, visualize etc. There are layers on information from what goes inside (cloud events), what the hell is my service sending/reciving (asyncapi) and what are the semantic meanings to all this stuff and easier discoverability (EventCatalog). Hope that helps!
English
1
0
0
75
Gunnar Morling 🌍
Gunnar Morling 🌍@gunnarmorling·
Wow, didn't you expect more than 50% to go with "What's CloudEvents?" Seems there's some evangelization to do for @CloudEventsIO. Thx to all who participated/replied!
Gunnar Morling 🌍@gunnarmorling

Question for my event streaming friends: are you using CloudEvents (cloudevents.io) in production? If yes, I'd love to learn more about your use case. You looked at it, but decided against it? Would love to learn more about that too 🙏!

English
1
0
6
2.3K
Cloud Events
Cloud Events@CloudEventsIO·
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: cloudevents.io/blog/2024-07-1…
English
0
3
10
628
Cloud Events ری ٹویٹ کیا
Richard Seroter
Richard Seroter@rseroter·
It's @thoughtworks Radar time! What hot and not? They suggest you adopt RAG, and CloudEvents. Go ahead and trial focusing on "health" over tech debt, Pulumi, OPA, Astro, Ray, and Gradio. Assess LLM-powered autonomous agents, using gen AI to understand legacy codebases, the Bun framework, and Ollama. Hold up on over-enthusiastic LLM usage, rush to fine-tune your LLMs, and LangChain. Full radar: thoughtworks.com/radar Blog post about trends in this radar: thoughtworks.com/insights/blog/…
English
0
4
14
2.2K