Compose vs Memcached Cloud: What are the differences?
What is Compose? We host databases for busy devs: production-ready, cloud-hosted, open source. Compose makes it easy to spin up multiple open source databases with just one click. Deploy MongoDB for production, take Redis out for a performance test drive, or spin up RethinkDB in development before rolling it out to production.
What is Memcached Cloud? A fully-managed service for hosting and running your memcached in a reliable and fail-safe manner. Memcached Cloud is a fully-managed service for running your Memcached in a reliable and fail-safe manner. Your dataset is constantly replicated, so if a node fails, an auto-switchover mechanism guarantees data is served without interruption. Memcached Cloud provides various data persistence options as well as remote backups for disaster recovery purposes.
Compose and Memcached Cloud are primarily classified as "MongoDB Hosting" and "Managed Memcache" tools respectively.
Some of the features offered by Compose are:
- One click, production-ready, cloud hosted MongoDB, Redis, Elasticsearch, PostgreSQL and RethinkDB, with additional databases in beta.
Every deployment features: database autoscaling based on data size usage - private VLAN, IP whitelisting, SSL, full-stack monitoring, custom alerts - HA and fault tolerance with automatic failover
On the other hand, Memcached Cloud provides the following key features:
- true high-availability
- fast storage engine
- backups and imports
"Simple to set up" is the top reason why over 41 developers like Compose, while over 5 developers mention "Heroku add-on" as the leading cause for choosing Memcached Cloud.
According to the StackShare community, Compose has a broader approval, being mentioned in 82 company stacks & 19 developers stacks; compared to Memcached Cloud, which is listed in 3 company stacks and 4 developer stacks.
What is Compose?
What is Memcached Cloud?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Compose?
What are the cons of using Memcached Cloud?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We went with MongoDB , almost by mistake. I had never used it before, but I knew I wanted the *EAN part of the MEAN stack, so why not go all in. I come from a background of SQL (first MySQL , then PostgreSQL ), so I definitely abused Mongo at first... by trying to turn it into something more relational than it should be. But hey, data is supposed to be relational, so there wasn't really any way to get around that.
There's a lot I love about MongoDB, and a lot I hate. I still don't know if we made the right decision. We've been able to build much quicker, but we also have had some growing pains. We host our databases on MongoDB Atlas , and I can't say enough good things about it. We had tried MongoLab and Compose before it, and with MongoDB Atlas I finally feel like things are in a good place. I don't know if I'd use it for a one-off small project, but for a large product Atlas has given us a ton more control, stability and trust.