You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by "kcheng.mvp" <kc...@gmail.com> on 2019/03/23 15:12:03 UTC

What's the difference between client node, jdbc driver and thin client

from the document 

client node: https://apacheignite.readme.io/docs/clients-vs-servers
jdbc driver: https://apacheignite-sql.readme.io/docs/jdbc-client-driver
thin client: https://apacheignite.readme.io/docs/java-thin-client


when a node runs with *client mode*, it will join the cluster topology.
when access ignite cluster with jdbc driver, it just behavior as a normal
database driver(as mysql jdbc driver)
when access cluster via * think client *, in the document it addresses that
* it does not join the cluster topology.

it seems there are are no difference between * jdbc driver * and * thin
client* expect for the * cache api*

for performance consideration: client node > think client > jdbc driver.

is my understanding correct?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: What's the difference between client node, jdbc driver and thin client

Posted by Denis Mekhanikov <dm...@gmail.com>.
In general client nodes have better performance than thin clients, but they
require more resources and have stronger coupling with the rest of the
cluster.
Thin client and thin JDBC driver have about the same performance, so
everything depends on a use-case.

So, your understanding is quite correct.

Denis

сб, 23 мар. 2019 г. в 18:12, kcheng.mvp <kc...@gmail.com>:

> from the document
>
> client node: https://apacheignite.readme.io/docs/clients-vs-servers
> jdbc driver: https://apacheignite-sql.readme.io/docs/jdbc-client-driver
> thin client: https://apacheignite.readme.io/docs/java-thin-client
>
>
> when a node runs with *client mode*, it will join the cluster topology.
> when access ignite cluster with jdbc driver, it just behavior as a normal
> database driver(as mysql jdbc driver)
> when access cluster via * think client *, in the document it addresses that
> * it does not join the cluster topology.
>
> it seems there are are no difference between * jdbc driver * and * thin
> client* expect for the * cache api*
>
> for performance consideration: client node > think client > jdbc driver.
>
> is my understanding correct?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>