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.
Redis is hot in the tech community right now. It's come a long way from being a small personal project from Antirez, to being an industry standard for in memory data storage. With that comes a set of best practices that most people can agree upon for using Redis properly. Below we'll explore 10 quick tips on using Redis correctly.
Redis Sentinel provides a simple and automatic high availability (HA) solution for Redis. If you’re familiar with how MongoDB elections work, this isn’t too far off. To start, you have a given master replicating to N number of slaves. From there, you have Sentinel daemons running, be it on your application servers or on the servers Redis is running on. These keep track of the master’s health.