Geek Answers Handbook

ElasticSearch: Jest vs Rest vs TransportClient vs NodeClient

I looked at the official documentation at https://www.elastic.co/blog/found-interfacing-elasticsearch-picking-client

But he does not give any tests or performance numbers to help choose among customers. And I find it non-trivial to configure TransportClient or configure NodeClient , because the documentation for this is also very rare, without any examples.

So, if someone has already done some benchmarking when choosing a client, I would really appreciate it and pay more attention to setting up an installed client, rather than evaluating which client to choose.

Our application is a write-heavy application , and for this we plan to create a 50-sharp, 50-replica ES-cluster .

+4
source share
1 answer

All these clients are suitable for requests, and they all have their pros and cons (the list below is not exhaustive):

  • A Node client provides a single hop in the cluster, but since it will also be part of the cluster, it can also cause too much chatter inside the cluster
  • A The transport client is not part of the cluster, therefore, two-pass feedback is required and is associated with one node at (from the list presented during its construction).
  • Jest - ES REST
  • , , Jest, , REST Spring REST, Apache HTTP ..

, . , , - - - , , .

, , .. ( ) (Kafka, Redis, JMS ..), ES. , - Logstash .

Kafka JMS Redis, Logstash ES, Logstash , .

, , . , , , , ETL ( Logstash, fluentd ..) .

UPDATE

, ES 5.0 Java REST-.

+2

More articles:


All Articles