We're excited to announce that the ObjectRocket for MongoDB Beta is now available in the Heroku Elements Marketplace.
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.