Posted: 17 Oct 2018 22:19 EDT Last activity: 20 Nov 2018 14:31 EST
Apache Ignite vs Hazel Cast
We are in process of updating Pega 7.1.9 to 7.4. My application is hosted on 32 JVM and all the JVMs are in one datacenter using Hazelcast for cluster communication . I am looking for details and
suggestion for Ignite vs Hazel Cast.
Which is better between Apache Ignite and Hazel Cast.
Any real time performance comparison.
Do we need additional hardware ?
what is the difference between embedded mode and client-server mode
Its better if you go with WebSphere Application Server which is has very good compatibility... or can go with JBossEAP if don't want in one cluster with 32 JVM's use as follows... Grouping nodes into partitions by assigning partition names enables you to break a large cluster up into several smaller clusters. Doing this should improve performance. For example, instead of having a cluster of 100 nodes, where all 100 nodes are trying to execute and refresh the same timers, you can create 20 clusters of 5 nodes by giving every group of 5 a different partition name.
I like your idea. We are using IBM websphere application with 32 jvm in one cluster. We have 16 application server and each application server have two node. In current setup, during deployment we bring down all the nodes except primary and deploy the code through primary node and bring back all the remaining 31 nodes. How the synchronization will work during the deployment if we break down one cluster into two or more.
1. you have Hybrid clustering in Production... which we won't recommend for Prod env:--- Yes we have hybrid cluster, I did not get your point. Is PEGA not recommending to have hybrid cluster in production? please hare more detail around it.
2. We are not moving away from WAS, but looking for
In general, Hybrid/mixed is not recommended in production env.. for example in your case when you built 5 JVM's in one server i.e, for one JVM at a minimum if you allocate 4GB, on the whole 20GB is going for only JVM's... hope you are using multi-core CPU ( at least 8 cores additional memory). This increases your server cost as well as more chances to fail multiple JVM's one go.
HazelCast is best one as open source in-memory data grid based on java, which is schema free. It support all OS with java VM. Support on- premise and on cloud. It offers open binary client protocol to supports apis for any binary programming language.