Adressing Objects in Medatarun

Object addressing in APIs is a user concern, not just a "purely technical" question. It directly affects ease of use (DX) and integration complexity, and therefore build and maintenance costs: our costs and our users' costs.

Using IDs or business keys is not a minor detail. Once the choice is made, it commits clients for the long term, often well after the API has gone into production.

The real issue is not choosing one over the other, but avoiding locking the API into that choice.

On Medatarun, I wanted to treat that as a contract and product architecture concern, not as a technical detail. Due to the nature of Medatarun as an integration tool, this question was there from the beginning: how can I make writing scripts and tools easier, with data coming from every part of the Information System.

I took the time to write down the reasoning here:

👉 Addressing objects in Medatarun

These decisions are invisible at launch. They only become noticeable when they haven’t been made.