Reputation: 206
I am concerned about the performance of ignite cache when running ignite sever as docker container and as Linux service.
And
Server - client approach vs ignite thin driver approach.
Please guide me which approach is better.
Upvotes: 0
Views: 265
Reputation: 1795
Check this section for tradeoffs between thick and thin clients. In short, the thick clients are faster and support all the Ignite APIs (at least for Java).
Upvotes: 1
Reputation: 1660
Regarding your question about thick
vs thin
comparison I can say that thick
client is faster in general because it communicates with an entire cluster (it's affinity aware), it means that network overhead is smaller in that case. And it supports more features than thin
client. But the drawback is that thick
client is full-fledged member of a cluster, it's not as lightweight as thin
client is.
The main idea about Docker
is that Docker
always has overheads compared to a pure Linux
installation. It will be slower in general.
The main point here is that you should measure performance to understand client and deployment types suitable for your use-case. It's pretty difficult to give some piece of general advice about performance-related stuff.
Upvotes: 2