Dharmjit

Ah nice! I will, Thanks.

Great, Is there some webpage, doc where I can read more about the differences between Json Schema and Json Structure?

The alternatives from elastic, microsoft and aws seems similar to gRPC in at least defining an IDL and generating code for client and server stubs. I think there is also a gRPC plugin to generate/serve OpenAPI APIs from protobuf definitions.

Is it the verbosity of the Go code or something else? I don’t have experience with other programming languages but it seems like a bit more verbose Go code makes it more intuitive…no?

Awesome and thanks for sharing it. I will try to keep an eye out for learning purposes and also any opportunities to contribute back :)

Thanks @clemens.vasters.com, we have started using cloudevents for an internal eventing platform. I will explore xregistry as event schemas are next in pipeline. I will go through the xregistry docs🙏

Interesting… just curious if there are any pointers on how it is different from other schema registries such as confluent, etc.

Oh man, it was really hard for me until sometime back. I am now trying/focusing to get my priorities right and keep reminding myself of those.

We are builing one with grpc bidirectional streaming apis, and we are just publishing those to kafka as they arrive with users/customers defined partioning key.

Conflicts atleast related to design/code implementation can be resolved via some spikes around tradeoffs.

If my peers can read and understand the code I have written easily just with code comments, function or var names, etc. without docs/diagrams, I guess I could say its quite there.

Yes, I had a similar experience in my previous org. Enterprises are pushing K8s everwhere but edge require specialized solutions tailored to its unique limitations and usecases.

This really is the key if someone working remotely wanted to grow in their career. I myself is working on this.

bad UX :)

So true, enterprises are avoiding opensource software for that specific reason and ends up building something similar.

We also use a similar pattern: a TestState struct with all the setup and cleanup logic.

I read it few days back, quite detailed and was a good read. Next is to read about sync.Map