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

Carmine v4 Cluster support #298

Open
ptaoussanis opened this issue Feb 5, 2024 · 6 comments
Open

Carmine v4 Cluster support #298

ptaoussanis opened this issue Feb 5, 2024 · 6 comments
Assignees

Comments

@ptaoussanis
Copy link
Member

No description provided.

@ptaoussanis ptaoussanis self-assigned this Feb 5, 2024
@ptaoussanis ptaoussanis moved this to Sep-Oct in 2024 Release roadmap Feb 5, 2024
@ptaoussanis ptaoussanis moved this from Sep-Oct to Nov-Dec in 2024 Release roadmap Feb 28, 2024
@ptaoussanis ptaoussanis moved this from Nov-Dec to Sep-Oct in 2024 Release roadmap Feb 28, 2024
@ptaoussanis ptaoussanis moved this from Sep-Oct to Nov-Dec in 2024 Release roadmap Mar 27, 2024
@ptaoussanis ptaoussanis moved this from Nov-Dec to TBD in 2024 Release roadmap Apr 18, 2024
@charan1973
Copy link

Hi @ptaoussanis. Can I pick this up? I can reach out to you on Slack if you need to discuss anything.

@ptaoussanis
Copy link
Member Author

@charan1973 Hi Charan, thanks for pinging about this!

What's your level of familiarity with Redis Cluster and the Redis protocol? I've got some of the groundwork already laid for Cluster support, but have a few non-trivial parts that still need to be implemented.

And don't currently use (or have any use for) Cluster myself, so testers would definitely be helpful + welcome later.

@charan1973
Copy link

At my current job, we use redis cluster for managing data. So I do have familiarity to work with it. I can setup and test on my machine.

Please let me know how I can help or any other details if needed.

@ptaoussanis
Copy link
Member Author

Great, that's good to know - thanks 👍

I'm not currently expecting to focus on Carmine v4 anytime soon, but later this year might be a possibility. When I do, I'll take a look again at the current state of Cluster support and will ping you then if there's something you might be able to assist with.

If you need Cluster support in the meantime, you may want to look at Jedis or one of the other alternative libs.

Cheers! :-)

@charan1973
Copy link

Thanks for the reply. The company service has been already moved to Jedis(I am not representing them). I liked carmine as it was easier to read compared to Jedis so thought of contributing during my free time and learn more.

No worries if you are working on it. Thanks 🙏🏼

@ptaoussanis
Copy link
Member Author

ptaoussanis commented Jan 10, 2025

Ah, gotcha 👍

So I'm definitely not actively working on it right now. Carmine v4's a huge amount of work, and there's been little interest in it expressed by the community - so I've mostly been working on it as a background task.

Most of the core is already usable, as is Sentinel support. I've recently deployed a project to production using the new core.

But there'd still be a ton of work (esp. documentation) to make this useful to typical users.

The Cluster implementation is the least developed since I have the least use for it myself. The core has been designed with Cluster support in mind though.

Basically: getting v4 usable, especially with Cluster support - would still be a lot of additional design and implementation work. Both would be non-trivially complex, so probably not an ideal candidate for user contributions unless the contributors are prepared to dedicate a lot of time+effort.

It's helpful though to see folks express interest and to offer to help test. I'm still planning my open source roadmap for the year, and definitely would like to get v4 publicly usable at some point. Just a matter of timing/prioritisation - have several big-ticket items I'd like to get done this year.

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

No branches or pull requests

2 participants