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] Named Pipes Backplane #355

Open
schmitch opened this issue Jan 8, 2025 · 1 comment
Open

[FEATURE] Named Pipes Backplane #355

schmitch opened this issue Jan 8, 2025 · 1 comment

Comments

@schmitch
Copy link

schmitch commented Jan 8, 2025

Problem

currently we do not use FusionCache, but we use IDistributedCache and created our own L1 cache on top.
our IDistributed cache is backed by https://www.nuget.org/packages/NeoSmart.Caching.Sqlite and https://www.nuget.org/packages/Microsoft.Extensions.Caching.StackExchangeRedis.

We have two deployement modes:

  1. single server (via sqlite3), but multiple processes on the same host
  2. multiple servers (via redis)

currently we are looking into fusion cache, but we would need a Backplane that would support ANY IDistributedCache via a Backplane that works on a single server, preferrably without new dependencies (like other databases, etc...)

Solution

we looked into https://learn.microsoft.com/en-us/dotnet/api/system.io.pipes?view=net-9.0 if it would be possible to use as a backplane and I think it would be a good fit to support it as a fast single node ipc implementation.

Alternatives

none

Additional context

none

@jodydonetti
Copy link
Collaborator

Hi @schmitch , thanks for the input: I'm reading about named pipes to look for common scenarios, usage patterns, edge cases and whatnot.
Anyway I like the idea, will let you know!

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

No branches or pull requests

2 participants