Transport Client VS REST Client

Elastic Stack Elasticsearch
1

Hi ,

I have started using elastic search , i have very basic question .
After Installing and running elastic search the server can be accessed in
two ways.

REST client i.e. using curl which listens at 9200
Transport Client or Node Client that listens at 9300.

  1. why do we need two different ways of accessing the same server?
  2. we can index, search , delete etc etc using REST client why do we need a
    transport client?
  3. what is the advantage of transport client over rest client ? which
    scenario we should use these clients?

Regards
Paul

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

1 Like
2

The transport client handles communication between nodes. The rest-client
is for http-api.

On Mon, Oct 14, 2013 at 7:29 AM, paul avinashpaul85@gmail.com wrote:

Hi ,

I have started using Elasticsearch , i have very basic question .
After Installing and running Elasticsearch the server can be accessed in
two ways.

REST client i.e. using curl which listens at 9200
Transport Client or Node Client that listens at 9300.

  1. why do we need two different ways of accessing the same server?
  2. we can index, search , delete etc etc using REST client why do we need
    a transport client?
  3. what is the advantage of transport client over rest client ? which
    scenario we should use these clients?

Regards
Paul

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Runar Myklebust
Enonic AS
Senior Developer

http://enonic.com/download

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

3

The NodeClient and the TranspotClient are basic Java clients. They can not
be accessed by Perl, Python, Ruby etc.

The REST HTTP client exposes the NodeClient so that ES can be used by all
languages who have a REST client.

Jörg
Am 14.10.2013 07:30 schrieb "paul" avinashpaul85@gmail.com:

Hi ,

I have started using Elasticsearch , i have very basic question .
After Installing and running Elasticsearch the server can be accessed in
two ways.

REST client i.e. using curl which listens at 9200
Transport Client or Node Client that listens at 9300.

  1. why do we need two different ways of accessing the same server?
  2. we can index, search , delete etc etc using REST client why do we need
    a transport client?
  3. what is the advantage of transport client over rest client ? which
    scenario we should use these clients?

Regards
Paul

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

4

The advantage of the TransportClient is that remote JVM can connect to ES
cluster(s) over configurable network interface without becoming a full
cluster node. This is useful for adding support of ES to Java 3rd party
software and it can scale independently of ES.

Jörg
Am 14.10.2013 09:07 schrieb "joergprante@gmail.com" joergprante@gmail.com:

The NodeClient and the TranspotClient are basic Java clients. They can not
be accessed by Perl, Python, Ruby etc.

The REST HTTP client exposes the NodeClient so that ES can be used by all
languages who have a REST client.

Jörg
Am 14.10.2013 07:30 schrieb "paul" avinashpaul85@gmail.com:

Hi ,

I have started using Elasticsearch , i have very basic question .
After Installing and running Elasticsearch the server can be accessed in
two ways.

REST client i.e. using curl which listens at 9200
Transport Client or Node Client that listens at 9300.

  1. why do we need two different ways of accessing the same server?
  2. we can index, search , delete etc etc using REST client why do we need
    a transport client?
  3. what is the advantage of transport client over rest client ? which
    scenario we should use these clients?

Regards
Paul

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.