Skip to content

switch all IDs from int64 to Guid (string)
Compare
Choose a tag to compare
@abdullin abdullin released this 06 Dec 12:56
· 7 commits to main since this release
v1.3.0
de595a2

In the previous versions, API and specs used sequential int64 as an ID. This created a bias towards event-sourcing implementations that have a monolithic shared state.

In this release we are switching all IDs from int64 to Guid (string) in API and specs.

When your code runs in test mode, it is expected that it will use globally unique ids for all entities (you can use a static singleton for that). For example, first product will get 00000000-0000-0000-0000-000000000001, first location created after it - 00000000-0000-0000-0000-000000000002.

For the sake of brevity, spec output will replace these with:

  • "00000000-0000-0000-0000-000000000001" -> UID(1)
  • "00000000-0000-0000-0000-000000000002" -> UID(2)

Unique identifiers are represented with a string type in our gRPC proto3 schema. This avoids problems with various platforms and byte orders.

Assets 7
Loading