Unfortunately that's not true: it depends directly on what you are doing with your RDBMS - there are many work loads which are better suited to MongoDB. Obviously there are also many which are not.
Unless I'm out of date, Redis and High Availability don't go together in the same sentence; awesome as it is, it's still a single point of failure.
Comments
Unfortunately that's not true: it depends directly on what you are doing with your RDBMS - there are many work loads which are better suited to MongoDB. Obviously there are also many which are not.
Unless I'm out of date, Redis and High Availability don't go together in the same sentence; awesome as it is, it's still a single point of failure.
> Unless I'm out of date, Redis and High Availability don't go together in the same sentence; awesome as it is, it's still a single point of failure.
Clustering is a work in progress (http://redis.io/topics/cluster-spec , http://redis.io/presentation/Redis_Cluster.pdf), replication is available (http://redis.io/topics/replication).
> Obviously there are also many which are not. that's exactly what i am saying.