Get the latest news and information about the ObjectRocket platform and its fully managed instances.
Free 30-Day Trial
Provision a single Redis (500MB), MongoDB with MMAPv1 (up to 5GB), or Elasticsearch with Kibana (512MB RAM / 4GB Disk) instance and experience the ObjectRocket platform backed by Fanatical Support® free for your first 30 days.
Anybody who looks at the ObjectRocket for Elasticsearch page should (hopefully) notice that we mention dedicated containers and our high-performance hardware environment a number of times. Last week we posted a performance comparison between ourselves and a couple of the other Elasticsearch services to give you some insight into the results of our design. Now that you've seen the results, I thought it was about time that we walked through the architecture, where we designed for performance, and the other considerations we had to keep in mind.
As data platforms continue to expand and transform there's one aspect that never seems to change; everyone still wants a backup copy of their data! The evolution of technology still demands a need to have access to backups in order to restore to a local development environment, a copy for safe keeping or compliance, and various other use cases. This walkthrough will show you how to leverage the S3 repository plugin with your ObjectRocket for Elasticsearch instance.
Best practice dictates that every database user should only be assigned a minimum set of privileges that on the one hand allows the user to fulfill their mission, and on the other hand minimises the impact of a security breach. For example: a database user used for reporting; it is not nessesary and doesn’t make sense to provide write access since read-only access is adequate.
Have you every spent time dreaming of a fully automated Elasticsearch environment? If so, stay tuned as this post will walk you through some of ObjectRocket's basic API features for our Elasticsearch product. Using the ObjectRocet API will allow you to create instances, users, acls, and more on demand.
A common question we're asked here at ObjectRocket is: "How do you compare to X?". This is a very good question, as you should always look for the best performing option for your business! We're always looking for ways to make our platform better and show what we can do.
Last month we launched Elasticsearch and Kibana 5.0 as an early access option for new clusters on ObjectRocket for Elasticsearch. Since then, we've been continuing to improve the experience and are now ready to remove the early access label and declare Elasticsearch 5.0 general availability on the ObjectRocket platform.
From day one at ObjectRocket, our mission has been to provide databases close to your application, no matter where it lives. Moving data is never fun, so we're always looking for ways to keep the service snappy regardless of which cloud our users use for their app tier, whether it's Rackspace, AWS, or any other cloud. However, another part of our mission is to provide high performance with our dedicated hardware architecture. That's where we hit a particular challenge... How do we keep our databases close to customers with applications in AWS, while being able to manage and maintain our own gear? The answer is AWS Direct Connect.