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.
When a company's customers, employees, and partners can access data easily through a user-friendly system, they have two people to thank for it: a database administrator and a data architect. Ensuring that well-built databases function reliably and securely for potentially thousands or even millions of users is a major responsibility, and companies in every industry rely on data architects and DBAs to design and monitor data networks that meet the needs of all who use them.
In this post, we'll explain some of the most common Redis use cases and different characteritics that are influencing these choices.