Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Distributed cache is eventually consistent (does not wait for L2) #1047

Closed
jmprieur opened this issue Mar 5, 2021 · 1 comment

Comments

@jmprieur
Copy link
Collaborator

jmprieur commented Mar 5, 2021

Eventual consistency is a programming model in which programmers make the assumption that over a long enough period of time and without changes to a system, the current version of a particular program will eventually distribute until every replica of the program is consistent.

Is your feature request related to a problem? Please describe.
Today the Distributed token cache adapter awaits for asynchronous operations on the underlying IDistributedCache

Describe the solution you'd like

  • Don't wait for write and remove operations.
  • This might require managing an event list of operations.

Describe alternatives you've considered
Task.Run() => { try/catch to do the operation} was tried out. See #1043

Additional context
See also Wilson's cache: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/1605/files

@jennyf19
Copy link
Collaborator

Released in 2.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants