Eugene,
> Also it looks like prior to 2.8.0 the Java thin Client was thread safe but
> single threaded , but since 2.8.0 the Java thin client is Multithreaded, (I
> have a book that mentioned it was not multithread, which confused me).
> Is this correct and why you suggest I only need one
Hi Dennis ,
Again thanks for you feedback and links these are very helpful.
Also it looks like prior to 2.8.0 the Java thin Client was thread safe but
single threaded , but since 2.8.0 the Java thin client is Multithreaded, (I
have a book that mentioned it was not multithread, which confused
Eugene,
In such a case, I would go for the thin client for several reasons:
- With the thick client (aka. standard client), you will come across
several limitations if the servers are deployed on VMs, but the thick
clients are running in a K8S environment. Those limitations are to be
Thanks for getting back to me on this Dennis,
The company's Ignite Cluster is already up and running on VMs on our
company network. The service my team is standing up will run in our Private
cloud K8S environment.
Regarding our usecase we will have say 2 or 3 caches, our service will be
passed 3
Hi Eugene,
Let me help you with that as much as I can. Please help me understand the
following:
- Is the cluster supposed to be deployed outside of Kubernetes (on VMs
or bare-metal)? Is this a private cloud (OpenShift, PCF) or a public
environment (Azure, AWS, etc.)?
- If you use
Hi Igniters,
Our company has recently started using Ignite and our team are now to it.
We would like to use Ignite as a Cache layer for an upcoming project
Our use case is that we have an Ignite cluster that we want to interact with ,
our client service is Springboot based and running in a
