Our thoughts about database management plus the latest information about the ObjectRocket platform.
Free 30-Day Trial
Provision a Redis (500MB), MongoDB with MMAPv1 (up to 5GB), and/or Elasticsearch with Kibana (1GB RAM / 8GB Disk) instance and experience the ObjectRocket platform backed by Fanatical Support® free for your first 30 days.
Database Administrators (DBAs) used to be the masters of their domain. They were the intermediary that stood between the databases necessary to conduct daily business and rest of the company. Not only were they the gatekeepers responsible for protecting the data but also the schemas that held that data. They were responsible for running the whole system, top to bottom, performing any task required to keep the database servers functional.
A question faced by a lot of companies as they start out (especially tech-based companies) is whether they want to outsource certain functions or do them in-house. Making this decision can sometimes be difficult, since it can seem expensive whether you’re hiring your own crew or paying another company to get it done.
Databases are essential to modern business. Every day, you’re generating data that needs organizing, indexing, storing, and eventually, retrieving. Your constant stream of customers and users feeds this data stream, growing your database, and increasing the number of requests on the system. Sometimes, though, traffic is higher than we expect, and those who aren’t prepared for a spike in server requests will ultimately suffer the consequences.
Are you trying to manage your databases in addition to generating the content that goes into it? Although there is something to be said for hands-on management, running databases in production can be hard and it can start robbing your business of time, focus, and money before you know it. Knowing when to outsource is key — especially when you have a small team and a limited budget.
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.
Update on Jan 20, 2017: In August 2016, we introduced Unlimited Availability of ObjectRocket Redis on AWS. Since that time, we have decided to leverage our existing Rackspace infrastructure for hosting Redis and End of Life the existing Redis on AWS infrastructure. However, we are now providing an AWS DirectConnect link bringing fully managed HA Redis closer to AWS customer's applications while offering the same core features that exist on Rackspace infrastructure. For more information on AWS Direct Connect, check out our blog post What Does AWS Direct Connect Have to do with ObjectRocket?
So you have a MongoDB data set, and you need a place to host it! As you've discovered, we have an impressive list of features, but up until this point, many of them have only been available for sharded instances. Some of the key features include 3 data nodes per shard, SSL connection options, WiredTiger storage engine, encryption for data at rest, and vertical scaling of resources. But if sharding doesn't fit your workload, your data schema, or your data volume, then it can be awkward or impractical to force yourself to use a sharded instance, when a simple replica set is what you really need.
For this tutorial on the new Redis GEO commands, we’re going a bit out of the box. Normally you might expect to see a tutorial showing you how to match users with local resources such as restaurants or hotels. For this we’re going to track runners in a marathon. This will showcase some of the more dynamic things you can do with Redis’ Geo support.
Location, Location, Location. We all carry around devices that can provide our specific location from almost any place on earth. If we treat this location as data, it can be a powerful tool. Applications and solutions that are location aware are not necessarily new and are becoming more common every day. Uber, Tinder, and Expedia are just a few examples of applications that leverage location. How developers use a geographical location in their applications varies depending upon the use case. Elasticsearch, MongoDB, PostgresSQL, and MySQL all have support for geospatial indexing in some way. With more solutions requiring “real-time” location, these solutions may either be complex to incorporate or not be performant enough to meet the requirements.
ObjectRocket Redis is now offering an additional level of security by providing the option of using SSL encryption between a customer’s client(s) and their ObjectRocket Redis instance(s). Customers will now have access to either a Public or ServiceNet connection string with or without SSL Encryption via the ObjectRocket control panel. This capability will give customers that want or need another layer of security the ability to encrypt traffic between their Redis client and the ObjectRocket Redis endpoint.
If you are looking to take advantage of the Spark's speed and ease of use, you owe it to yourself to try our Rackspace optimized Spark Stack. Spark combined with Tachyon and Zeppelin culminates into a very fast and easy-to-use option. In addition to this stand alone Spark Stack, we also have versions that are bundled with Hortonworks Data Platform, for those wishing to use Hadoop and Spark on the same cluster.
Today I am excited to announce we have added a new capability to our Managed Cloud Hadoop and Spark Service. In the past our users would provision their Hadoop or Spark clusters based on some pre-defined stacks we had created. While this worked for many of our users, there were others that wanted more flexibility and more control. To that end, we have been working for the last year on an entirely new provisioning system that would allow our customers to create fully customized stacks. This now means instead of settling for the default values for number or size of master services nodes, users now have the ability to define the individual node sized and how many of each. You want 3 name nodes instead of 2? No problem. You want 8GB of memory per name node instead of 4? No problem. You want to create a stack that has your ideal configuration of services, such as Spark with Kafka, and Zepplin, but not some of the other components that come by default? No problem.
Our mission at ObjectRocket is to provide the fastest, most reliable databases available. There are plenty of great places to run your applications, but the role that containers (and Docker in particular) play in the enterprise today is undeniable. Rackspace recently released a great new service called 'Carina', providing a high performance hosted Docker Swarm service that complements ObjectRocket very well. In this post, I'd like to show you how to get started deploying and scaling applications on Carina, while easily integrating with blazing fast databases on ObjectRocket.
Since we launched our ObjectRocket Elasticsearch service this past July, we have been hard at work in the garage, wrenching on some new features to add chrome to our Elasticsearch rocket. We are pleased to announce the following new features:
One of the most exciting developments over the lifetime of MongoDB must be the inclusion of the WiredTiger storage engine in MongoDB 3.0. Its very design and core architecture are legions ahead of the current MMAPv1 engine and comparable to most modern day storage engines for various relational and non-relational stores. One of the most compelling features of the WiredTiger storage engine is compression. Let's talk a bit more about performance and compression.
In our Employee Highlight series, we will introduce you to various ObjectRocket Team Members. This week we have Chris Lalonde, ObjectRocket co-founder & General Manager. Chris has 16+ years of experience building online platforms and an award-winning background, comprised of serial successes driving technology development and operations for a variety of startups, government agencies and Fortune 500 corporations. He has held senior executive positions with companies including Bullhorn, Quigo and online auction powerhouse, eBay. Chris has been awarded 5 patents.
When ObjectRocket announced the launch of tiered pricing for sharded MongoDB plans, we promised that we’d soon be doing the same for our Redis and Elasticsearch products as well. Today, we are delivering on that promise!
The latest major release of MongoDB had several great new features. The most significant among these was the inclusion of pluggable storage engines, and the first official one was WiredTiger. Since its release with MongoDB 3.0, WiredTiger has been getting tinkered on to increase its stability and we here in the dungeons of engineering at ObjectRocket have been turning wrenches on it as well. We are pleased to announce that we are now offering Early Access to WiredTiger as a storage engine option with MongoDB 3.0 in our East Coast and London datacenters, in addition to the default engine, MMAPv1. While other providers maybe a little hesitant to offer you new features...
"In general, Redis is not optimized for maximum security but for maximum performance and simplicity." This statement is taken directly from the Redis.io documentation on Redis and Security. Understanding this first and foremost helps set the stage for a discussion on ObjectRocket Redis functionality as it relates to security.
In our Employee Highlight series, we will introduce you to various ObjectRocket Team Members and this week we have Vanessa Taylor who is our Office Manager, she is responsible for managing facilities and office operations and without her we would be lost.
Do you have a brand new Elasticsearch instance, but all your useful data you'd like to search lives in a CSV file? No problem - Logstash makes turning almost any data into something easily searchable in an Elasticsearch index.
The ObjectRocket engineering team has been busy building our latest high performance data platform for taking full advantage of the new MongoDB 3.0 feature improvements. As with any major version upgrade, we suggest that you begin testing with MongoDB 3.0 prior to going straight into production and reach out to us with any questions.
As simple as Redis is designed to be, the complexity that Redis users face can get very real, very quickly. One of our mantras at ObjectRocket is to stay out of the way of Redis to allow it to perform and provide customers flexible tools to manage their instances. We are proud to announce the release of the Instance Resize feature. We built this feature to allow customers the ability to resize their instance(s) when it is best for them. A customer's memory needs for their Redis instance(s) is not always constant given their use-case. Whether customers are seeing spikes in traffic or have more permanent Redis size requirements, they need an easy and efficient way to resize their instances based upon their timeline.
Yesterday, June 4th, a Redis release was done to fix a Lua vulnerability which gave those with access to a Redis server the ability to break out of Redis and run arbitrary code. Read on to learn why your ObjectRocket Redis instances are not at risk and details on the vulnerability itself.
Instead of a social life, us engineers down in ops have been working on some new things. The latest and greatest of which is something we are calling ObjectRocket Dedicated MongoDB. We're talking about full cabinets of dedicated hardware, fine-tuned to work specifically with MongoDB to be as fast as possible, for a single customer, and they are ready to take off.
RedisConf is just around the corner! We’ve got a full day of inspiring keynotes, intensely practical sessions,
and plenty of fun networking when we gather next Thursday, March 5th, at the Innovation Hanger located at 3601 Lyon Street in San Francisco. With over 300 registrants and 20 speakers from big names like Hulu, Pivotal, Heroku, VMware and RedisLabs, it’s an event you don’t want to miss.
Jens Heyens, Kai Greshake, and Eric Petryka at CISPA recently published a paper entitled "MongoDB databases at risk - Several thousand MongoDBs without access control on the Internet". The paper outlines that basic security practices have not been followed by a large number of internet accessible MongoDB installations.
Over the past couple of months we have had a number of Rackspace customers ask us when they will have the ability to connect to their ObjectRocket for Redis instances over ServiceNet, and we are excited to launch this feature today in our Virginia (IAD), Dallas (DFW), Chicago (ORD) and London (LON) regions.
Today, we're excited to announce a new addition to the ObjectRocket platform - ObjectRocket for Redis. Redis is built for high performance, has versatile data structures and great documentation allowing developers to easily integrate Redis into highly scalable application stacks. We use it internally and so do many of our customers who have been pushing us hard to release a Redis Database as a Service offering.
For a number of months ObjectRocket has had a handful of customers helping our team develop integration with New Relic. Offering a suite of software analytics products, New Relic helps their customers gain actionable, real-time business insights from the billions of metrics their software is producing, including user click streams, mobile activity, end user experiences and transactions.
The ObjectRocket team has had a busy few weeks rolling out new capacity, and now we're very happy to announce that ObjectRocket instances are available directly in the Rackspace Chicago (ORD) datacenter!
ObjectRocket is a "Database as a Service" (DBaaS) based on the popular MongoDB database. What makes ObjectRocket completely different from other competitors in this space is that we have built the infrastructure from the ground up to ensure the best possible cloud database experience.
A few weeks ago the folks at Memsql introduced a new benchmark to show off the performance of their new product named 'bench'. They included a MongoDB option in the benchmark, and a blog post with some performance results.