Elasticsearch's introduction of a Java REST client in version 5.0 aims to provide a more lightweight and loosely coupled alternative to the existing transport client, with fewer dependencies and a more stable API. Performance benchmarks were conducted to compare the Java REST client and the transport client, focusing on throughput and latency during bulk indexing and search operations. The benchmarks used a "noop" Elasticsearch plugin to emphasize client performance, revealing that the Java REST client performs slightly below the transport client under lab conditions, particularly in bulk indexing. However, real-life tests show similar performances between the two clients, with the REST client achieving a sustainable throughput of around 1,200 operations per second compared to 1,700 for the transport client. Despite these initial differences, the Java REST client demonstrates promising performance characteristics for practical applications, with ongoing improvements anticipated to enhance its capabilities further.