The Problem:#

I ran into an interesting problem today when trying to handle a particularly hellish scenario¹. The situation is thus:

• I'm spinning up a new API service (using ASP.NET)
• We are re-using a bunch of existing infrastructure, including:
  • Our business-modelling graph database (we use Memgraph), and
  • Some C# libraries that define our interface with that DB, and a bunch of API helper services
• For primarily historical reasons², said graph database models most entities that are accessible via the API as nodes that have two IDs.
  • One is an internal ID (arbitrary, auto-assigned by various databases over time)
  • The other is a publicly-shared UUID³ (that we give customers and is used in our API's I/O)
    continue post →