Replies: 2 comments 1 reply
-
I suppose that the next logical step would be to also be able to run a celery worker. Maybe this is all out of scope for this project though. Feel free to close this if you think so. Thanks for all your work! |
Beta Was this translation helpful? Give feedback.
-
@thuibr I frankly think acting as a Redis instance would be definitely out of scope for the project. What might happen in the future, given RSGI is designed primarily on Granian itself, is to introduce a broadcasting feature to simplify the creations of channels and share websockets, and eventually add this capability also to ASGI proposing an extension for it, but that would be an alternative implementation of channels, not a shared memory interface for its storage needs. And also, I'm actually talking about a remote future, this is definitely something I don't expect to see coming shortly. |
Beta Was this translation helpful? Give feedback.
-
I think it would be so interesting if Granian could also act as a Redis server. So much now depends on Redis being a part of the stack, from Django caching to Django Channels to Celery. I don't have time to take a stab at this, nor do I really know Rust, but Rust and Redis are interests of mine for future projects.
CodeCrafters has its Redis project free for this month, which would be a good way to get up to speed. I also know that there are several Redis-compatible implementations out there. I wonder if a.) a Redis-compatible service could be built from the ground up in Granian, or b.) another implementation could be integrated into Granian.
I am just trying to start a discussion and see if there's any interest from the Granian maintainers and/or from somebody willing to take on this work.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions