> In whatever common code you have for your RPCs, add the ability for an RPC message to be traced. Because I realized API calls (which are just RPCs) need this

> In whatever common code you have for your RPCs, add the ability for an RPC message to be traced. Because I realized API calls (which are just RPCs) need this (which is a defacto feature of programming language through exceptions and stacktraces), I now think it is better to start at the programming language level, write your function normally, and then compile it to call/respond as an API endpoint. Actually I think it's best to write a monolith and then cut it s different pieces into independent microservices using code generation/manipulation, even though one's first intention is to build an ecosystem of microservices.