Congratulations. Hopefully, if you’re reading this, you recently signed up for Qbox Elasticsearch Hosting.
The first step to taking advantage of Qbox for your usage case is to provision a node from your dashboard.
If you’re still unsure of anything, I will personally ensure that a success manager is assigned to your account. Just email me: mark [at] qbox [dot] io. The transcript is below the embed.
Hey, This is Mark Brandon, CEO and Co-Founder of Qbox, demonstrating the Qbox platform.
Just to reiterate our value proposition, we provide managed instances of Elasticsearch, the open source data exploration and analytics platform. If you think about what Mongolab is for MongoDB, Cloudant is for CouchDB, or RedisLabs is for Redis, we are to Elasticsearch. We strive to relieve you of the dev-ops headaches so that developers can focus on building their search app.
So, let’s start. Here we are at the Qbox dashboard. You can see that I have two clusters active, one for a movie search demo, and another for an e-commerce demo. Here is the cluster name, the infrastructure provider, the Region, the version, and the cluster size.
It’s worth noting here one of our competitive advantages versus the competition. We are available in all data centers on AWS, Rackspace, and Softlayer. This is important because Elasticsearch is often used in conjunction with a primary data store and other apps, and so it’s important to our customers to be in the same data center as their other infrastructure. It helps with performance, stability, and bandwidth costs.
If I wanted to provision a new cluster, first I choose the Infrastructure provider. For this demo, I’m going to choose Softlayer. I’ll name this cluster analytics, and choose Softlayer’s Dallas data center. Over here, I can specify both the number of nodes and the resources on that node. A good production-ready cluster has 3 nodes for sharding and replication purposes and I’m going to choose 4GB RAM. Over here, you can specify your security parameters.
Now, another feature that sets us apart is the ability to install several different plugins from the Elasticsearch Community. This is an important differentiator. You can choose your rivers to existing data stores. Full-text plugins for non-western alphabets, and many more. I’m going to enable Kibana, the very awesome visualization plugin that is part of the ELK stack. Then, I create my cluster.
You can see now that after a few minutes, the cluster has been spun up. Now, since this is brand new, I haven’t configured it, so I’ll show you how to manage one of these other clusters.
WIth the movie search demo, you can here the cluster endpoints. This is a critical piece for communicating through the API. To monitor this cluster, I click here and you can see such items as index status, cluster health, shard status, node diagnostics, and so on. I lack time to go into depth on these, so for now, we thank you for watching.