thearchitectdev/architect.identities

Reliable unique ID generation for distributed applications.

architect.identities's Issues

AesPublicIdentityConverter Suggestion

First thank you for this generator, I tip my hat to you, as I thought of crafting one myself until I found this.

Regarding public identities the AesPublicIdentityConverter is marked internal. While the ServiceCollection extensions can wire up the IPublicIdentityConverter with its options this hard coupling prevents using an alternative approach such as using SimpleInjector or something like Pure.DI.

Please consider a new extension method that would expose a factory method (returning the IPublicIdentityConverter to prevent leakage) so other IoC & DIP approaches can be used.

Regarding Blazor WASM consider adding the attribute [UnsupportedOSPlatform("browser")] as AES even as of .net 7 rc2 does not support it, perhaps as a diagnostic report.

Question on distributed system

Hi, great project, but something is not clear, assuming that two machines generates a distributed id at the same millisecond, the timestamp part will be the same, there will be no monotonic increment since there is no centralized coordinator right?.

Also is this project a hobby/test or will it get long time support?. I am kind of thinking in using it instead of ULIDs but i am afraid that it will later get archived or forgotten.

Thanks.

SQLite :: decimal.ToAlphanumeric() causes exception

Hello! 😀

Thank you so much for sharing and maintaining such a great library!

Faced one problem when using SQLite database provider with EF and wonder if you could give suggestions on how to resolve it.

When using SQLite, decimal IDs are stored as "text" despite invocation of ConfigureDecimalIdTypes(). I believe that's because SQLite does not support DECIMALS with such high precision. When ID value is stored in the database, looks like ToString() generated method is used to convert number to a text database type:

public override string ToString()
{
  return this.Value.ToString("0.#");
}

As a result, decimal value is stored something like this: 1098956916504943605256135935.0 (note the trailing ".0").

Now, when trying to call ToAlphanumeric() on that value, exception is thrown:

System.ArgumentException: The ID must be positive, have no decimal places, and consist of no more than 28 digits. (Parameter 'id')

Looks like it does not like trailing decimal place ".0".

How would you suggest to resolve this? Either not store decimal place in the database or modify ToAlphanumeric() to disregard it?

Thank you! 🙏