I appreciate that this isn't the right approach for clients, but most backend stuff today really is synchronous request-response path you can model as a DAG. It's entirely the right approach for these kinds of applications.
Comments
Log in with your Bluesky account to leave a comment
Oh I agree! I don't even fault the tooling for assuming this: backend distributed tracing is overwhelmingly the primary use case for OTel.
My issue is that in some circles, the initial assumption got calcified into dogma despite the spec allows for more flexibility. I just want alternatives.
Comments
My issue is that in some circles, the initial assumption got calcified into dogma despite the spec allows for more flexibility. I just want alternatives.