Skip to content

RHAPSODY DataBackends with RADEX - #40

Merged
AymenFJA merged 2 commits into
mainfrom
examples/rhapsody-databackends
Aug 26, 2026
Merged

RHAPSODY DataBackends with RADEX#40
AymenFJA merged 2 commits into
mainfrom
examples/rhapsody-databackends

Conversation

@AymenFJA

Copy link
Copy Markdown
Collaborator
  • Demonstrate RedisDataBackend/DragonDataBackend launching the store and handing off its endpoint to a RADEX client (RedisClient/DragonClient),
  • With the exchange executed as RHAPSODY tasks via Concurrent/Dragon execution backends.

Demonstrate RedisDataBackend/DragonDataBackend launching the store and
handing off its endpoint to a RADEX client (RedisClient/DragonClient),
with the exchange executed as RHAPSODY tasks via Concurrent/Dragon
execution backends.

@MattToast MattToast left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Examples look great!! Thanks for helping show how radex can be used in the larger rhapsody ecosystem!!

Comment thread example/rhapsody-exchange/dump.rdb Outdated
@AymenFJA
AymenFJA merged commit 4558c91 into main Aug 26, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants