Redis: Garnet Pub/Sub capability spike (#170) - #178
Merged
Conversation
Prove in-process Microsoft.Garnet supports classic SUBSCRIBE, PSUBSCRIBE, and PUBLISH via StackExchange.Redis without introducing product APIs or pack dependencies.
Avoid a misleading same-multiplexer fan-out check and rely on SubscribeAsync acknowledgement before publish.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
eng/spikes/GarnetPubSubin-process probe for classic Redis Pub/Sub (SUBSCRIBE/PSUBSCRIBE/PUBLISH) against Microsoft Garnet via StackExchange.RedisTest plan
dotnet run --project eng/spikes/GarnetPubSub/GarnetPubSub.Spike.csproj -c Release→ OVERALL PASSCloses #170
Note
Low Risk
Eng-only spike with isolated MSBuild/package wiring; no production Redis API or shared dependency graph changes.
Overview
Adds
eng/spikes/GarnetPubSub, a standalone console probe for issue #170 that starts an in-process Microsoft.Garnet server and exercises classic Redis Pub/Sub through StackExchange.Redis (SUBSCRIBE,PSUBSCRIBE,PUBLISH). The harness prints per-family pass/fail and exits 0 only when all probes succeed, with a console DECISION line on whether Garnet is locked for Observables.Redis E2E.Isolation is explicit: local
Directory.Build.props/Directory.Packages.propsopt out of repo CPM and shared defaults; Garnet and StackExchange.Redis are pinned only on this spike project and are documented as not for pack graphs orObservables.BuildManifest.json. No Observables.Redis product API changes.Reviewed by Cursor Bugbot for commit 915b5ba. Configure here.