Not if you use a language that bans implicit type conversions (like go)
At any one point the data can interact with other systems, travel through codebases each seeing the data through their types, legacy APIs, the same-(ish) new-(ish) RPC API and in each service the data is represented in its own internal quirky way.
Sure, throw Go in that mix, hell at this point the more merrier! :)