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: github.com/xregistry/spec/tr…
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: github.com/xregistry/spec/tr…
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
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.
github.com/JustSteveKing/clo…
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-…
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/bl…
RT GaryStafford: Great overview of KnativeProject (k8s serverless platform) and CloudEvents (specification for describing event data), part of the latest ThoughtWorks Technology Radar Sneak Peek, by zhamakd of thoughtworks