Accessing Elasticsearch is easy since it’s just HTTP plus JSON! Be aware that this implies that it’s also easy to build an Elasticsearch client that performs poorly. There are a number of important considerations when choosing an Elasticsearch client. Is connection pooling with keep-alive being used? If not, setting up and tearing down HTTP connections, especially with SSL, will be expensive. Are bulk operations supported and used? Is your development team aware of and using synchronization best practices? If not, performance may be poor and data may wind up missing.