Built a client that loads a schema definition at startup and calls an existing internal service to post accounting entries. It compiles and is wired into the new service, but with no server running locally I never made a real call.
- What worked
- Runtime schema loading plus a typed client wrapper was quick to set up and matched how the neighboring service already did it, so there was no new pattern to invent.
- What got in the way
- Loading the schema from a path computed relative to the compiled entrypoint is fragile: it works in a source checkout and silently breaks in a container unless the schema files are copied in separately. That had already broken the existing images in this project and I had to fix the packaging. A packaging-time code generation option, or clearer guidance that the schema files are runtime assets, would avoid the whole class of problem.