Elasticsearch Overview

What is Elasticsearch?

Elastic.co defines Elasticsearch as a distributed, open source search and analytics engine, designed for horizontal scalability, reliability, and easy management. It combines the speed of search with the power of analytics via a sophisticated, developer-friendly query language covering structured, unstructured, and time-series data. The Elasticsearch ecosystem goes far beyond the Elasticsearch engine and also includes visualization tools (Kibana), logging tools (Logstash and Beats), and more.

What’s included in an ObjectRocket for Elasticsearch instance?

Starting with many NoSQL data stores like Elasticsearch is easy, but daily administration, monitoring, backups, and scaling can add a heavy and challenging workload to already overtaxed teams. We take the operational burden off of your team with our purpose built platform and 24/7/365 Fanatical Support so you can focus on using Elasticsearch and not keeping it up and running.

When you create an “Instance” in the ObjectRocket UI, what you’re actually getting is an 11-node Elasticsearch and Kibana cluster.

_images/elasticsearcharch.png

That’s 11 nodes minimum, for every plan size, on their own containers on different hosts. We split these hosts up four ways:

  • 2 Data nodes: To start, every cluster has a minimum of two data nodes. When you pick a Plan for your ObjectRocket instance, these are the nodes that get those specs. These nodes store the actual data for your instance and perform the majority of the data-related operations of your cluster. When you need to grow your cluster, these are the nodes that scale out and up.
  • 4 Client nodes: In Elasticsearch terms, these are technically coordinating only nodes, but in our architecture they do a lot more. Each one of these nodes acts as a coordinating only node, a layer of security (ACL enforcement and user authentication), and ingest node. These are the only nodes in your Elasticsearch cluster with internet, Rackspace ServiceNet, and AWS Direct connect access.
  • 3 Master nodes: These three nodes are dedicated to performing the master role in the Elasticsearch cluster.
  • 2 Kibana nodes: To support Kibana, we also include two dedicated Kibana nodes, which run Kibana in an active-passive, redundant setup. Like the client nodes, these nodes also serve as a layer of security by enforcing ACLs and user authentication for the Kibana nodes themselves.

How is pricing calculated on ObjectRocket for Elasticsearch instances?

In an ObjectRocket for Elasticsearch cluster, there are four things that impact the monthly price you pay: the datacenter you select to host your instance, the plan size for your data nodes, whether encryption at rest is enabled, and finally, total Elasticsearch data on the platform. There’s a pricing calculator that you can use to figure out the final price of an ObjectRocket cluster, but this section will outline how that price is calculated.

  • Region: When you create a new instance, you will select a datacenter/zone to host the instance, which fall into multiple regions. Each region charges a slightly different base rate for each plan size. Right now, the two regions that support Elasticsearch clusters are the US and UK. The pricing calculator linked above will show you the rates in each region.
  • Plan Size: Each plan size has a monthly subscription rate which then applies to each data node in the cluster. That subscription rate is only charged per data node. Client, master, and Kibana nodes are included in the data node rate and not billed separately.
  • Encryption: If you’ve enabled encryption at rest on your instance, then an additional 10% is added to the cost of that cluster.
  • Volume Discounts: As you grow your ObjectRocket footprint we apply tiered rate discounts based on the total amount of Elasticsearch storage you have on the platform.

Other than those four factors, everything else is included; 24x7x365 support, free migrations, and hosted Kibana are all part of the standard price.