hazelcast
Make possible to use CP subsystem in Community Version again
There are actually a lot of people who prefer Hazelcast over another solutions like ZooKeeper, Redis and another because of it great architecture, brilliant idea, embedded mode and lot of other benefits. And one of the greatest feature was Cluster Locks without using 3rd party external services. And we used it for a long time and there are lot of projects that depends on this feature. I completely realize of whole complexity of that solution to build precise cluster lock subsystem, but dont think that its a main reason to hide it under enterprise license. Companies who pay for enterprise version mainly want to get enterprise level of support and not for just CP subsystem. CP can be implemented via another free tools. But anyway I just want to kindly ask you (and i suppose whole community will support me) do not take great old features from the community and rather bring brand new features under the Enterprise License.
I agree with you, if lack of cp system, most new users will choose another system like ignite at the beginning of their business. and it will be very hard to change back to Hazelcast in the future.
it's annoying to think we have to introduce another tool because of this change... at this point might just as well switch to apache ignite
it's better to rethink about the business strategy, for new user or startup small business always care about functions first, not very large scale. after verifying their business model , or get a good revenue from market then they will need to scale their Hazelcast nodes. so the community license can limit the number of nodes , and open full functions, enterprise license support ultimate nodes and official tech support.
@davidwxy "most new users will choose another system like Ignite" <- exactly what we are going through right now. Start wtih Hazel but are now investigating Ignite as an option. Hazelcast is awesome though, so much easier to grok but yanking CP and then the noise on deprecating the Spring Integration module has us concerned.
yes, we are starting to look into newly released Ignite 3 as well, thinking to rewrite the whole project from Hazelcast to Igntie
Should at least allow use of "CP subsystem" features that can be used in "unsafe mode"...
Hi guys, I’ve already migrated to Ignite 3. The workload wasn’t too heavy, and everything is running smoothly so far. Good luck to you all!
Hi guys, I’ve already migrated to Ignite 3. The workload wasn’t too heavy, and everything is running smoothly so far. Good luck to you all!
hi @tixo we are evaluating this option as well now. Do you have in your setup an embedded cluster configuration for ignite 3? (meaning starting cluster nodes from java)
Was planning on bringing in Hazelcast for my project over this past week, seemed like a great fit.
This sealed the deal that I will use something else.
Oh well, guess it will just become some legacy cruft that no new projects bother with.
if hazelcast has proven something over the past few years, is that no one will care about this, ever.
