Skip to content

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

Closed

Description

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions