By “mostly transparent” I was mostly thinking type safety, ergonomics, no hand written boilerplate, etc. Totally fine to support a limited set of primitives an

By “mostly transparent” I was mostly thinking type safety, ergonomics, no hand written boilerplate, etc. Totally fine to support a limited set of primitives and collections passed by value, and require developers consider the failure modes. In my experience HTTP+JSON or gRPC are usually lacking in at least one of those respects. If you constrain all the services to be the same language it becomes easier.