Clustering for NodeBB enabled
-
@DownPW @Madchatthew this is worth reviewing
-
@phenomlab That looks very promising and the performance looks amazing. So after going to the website, this looks like this is basically MS version of Redis and uses most of the same commands and such, but they have been able to make it perform better which is very nice. One of my hesitations would be that it is MS and where is the code that grabs all of your data and information and will they in turn try to monetize this somehow in the future thus having to make a change again? I do like that you are able to use this with what is currently out there for Wordpress and should even work for Nodebb as well according to the documentation. You would just have to double check that the commands that are being used for Redis are being used for Garnet. There was a section about that. Still probably worth checking out and testing out though.
-
I don’t know… Not sure to use it?
Must test before
-
@phenomlab That looks very promising and the performance looks amazing. So after going to the website, this looks like this is basically MS version of Redis and uses most of the same commands and such, but they have been able to make it perform better which is very nice. One of my hesitations would be that it is MS and where is the code that grabs all of your data and information and will they in turn try to monetize this somehow in the future thus having to make a change again? I do like that you are able to use this with what is currently out there for Wordpress and should even work for Nodebb as well according to the documentation. You would just have to double check that the commands that are being used for Redis are being used for Garnet. There was a section about that. Still probably worth checking out and testing out though.
-
@Madchatthew Yes, I admit I had similar reservations, but there is also KeyDB, and Dragonfly
@phenomlab Those both look good. If you had to switch from Redis, which one of those options would you use?
-
@phenomlab Those both look good. If you had to switch from Redis, which one of those options would you use?
@Madchatthew probably KeyDB, but both seem to be strong contenders. Dragonfly also claims to be the fastest.
-
@Madchatthew probably KeyDB, but both seem to be strong contenders. Dragonfly also claims to be the fastest.
@phenomlab The only thing with Dragonfly is that they have the pricing side, which makes me wonder if that could at some point affect the open-source side. But maybe the pricing is just to have the option to have it on the cloud. But usually when there is money involved like that, at some point it usually affects the free side.
With that being said though, since they are both Redis forks, it would be pretty easy and seamless to switch from one to the other if needed. I am also wondering what the impact would be of using either of these with a Wordpress site? According to Dragonfly, it should be able to make Wordpress even faster with the faster performance. All of that will also depend on the server of course too and internet connection and what have you, but maybe use up less resources if the throughput is faster and multi-threaded.
-
@phenomlab The only thing with Dragonfly is that they have the pricing side, which makes me wonder if that could at some point affect the open-source side. But maybe the pricing is just to have the option to have it on the cloud. But usually when there is money involved like that, at some point it usually affects the free side.
With that being said though, since they are both Redis forks, it would be pretty easy and seamless to switch from one to the other if needed. I am also wondering what the impact would be of using either of these with a Wordpress site? According to Dragonfly, it should be able to make Wordpress even faster with the faster performance. All of that will also depend on the server of course too and internet connection and what have you, but maybe use up less resources if the throughput is faster and multi-threaded.
@Madchatthew I think there’s always that same danger no matter which open source solution you go for. By its very definition, open source comes at significant cost to the maintainer in terms of time, effort, and knowhow, so they often release a paid version of the product as a means of recovering some of that invested time in the form of revenue.
It’s when the commercial product requires more attention than the open source version that causes conflicts, and that version is often the casualty.
-
@Madchatthew I think there’s always that same danger no matter which open source solution you go for. By its very definition, open source comes at significant cost to the maintainer in terms of time, effort, and knowhow, so they often release a paid version of the product as a means of recovering some of that invested time in the form of revenue.
It’s when the commercial product requires more attention than the open source version that causes conflicts, and that version is often the casualty.
@phenomlab said in Clustering for NodeBB enabled:
@Madchatthew I think there’s always that same danger no matter which open source solution you go for. By its very definition, open source comes at significant cost to the maintainer in terms of time, effort, and knowhow, so they often release a paid version of the product as a means of recovering some of that invested time in the form of revenue.
It’s when the commercial product requires more attention than the open source version that causes conflicts, and that version is often the casualty.
This makes sense. Then unless you can get some people to help you maintain and update the code you are doing it all yourself and that takes up time to not being able to implement new features and now you are using more resources because you have more people helping and such. It all multiplies and pretty soon you either have to abandon it or come up with a way to make money to keep everything going.
-
@phenomlab said in Clustering for NodeBB enabled:
@Madchatthew I think there’s always that same danger no matter which open source solution you go for. By its very definition, open source comes at significant cost to the maintainer in terms of time, effort, and knowhow, so they often release a paid version of the product as a means of recovering some of that invested time in the form of revenue.
It’s when the commercial product requires more attention than the open source version that causes conflicts, and that version is often the casualty.
This makes sense. Then unless you can get some people to help you maintain and update the code you are doing it all yourself and that takes up time to not being able to implement new features and now you are using more resources because you have more people helping and such. It all multiplies and pretty soon you either have to abandon it or come up with a way to make money to keep everything going.
@Madchatthew True. I think this is the reason as to why most Open Source projects are abandoned because they are not sustainable in the long-term.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (ether email, or push notification). You'll also be able to save bookmarks, use reactions, and upvote to show your appreciation to other community members.
With your input, this post could be even better 💗
RegisterLog in
