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. Learn more
At ObjectRocket, our vision is to offer our products and support where our customers’ applications live. We’re excited to announce the availability of ObjectRocket Redis on the AWS infrastructure. This is the first of many services to come giving customers choice in who manages their data regardless of the cloud on which it lives.
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.
The standard redundant Redis solution is to run master/slave replication with
Sentinel managing the failover. This is expected to be followed up with either
a) Client support and use of Sentinel to discover the current master or b) A
TCP proxy in front of the Redis pod which is managed by Sentinel to point to
the master. The former is the ways Redis Sentinel is designed and the latter is
a growing trend - and the way ObjectRocket Redis is configured.
In this post I'm going to show how to quickly and easily create a Data Connector between your ObjectRocket MongoDB instance and your ObjectRocket Elasticsearch instance. Then I show you how to view your data within a custom Kibana dashboard.