What is Compose?
Who uses Compose?
Why developers like Compose?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Compose in their tech stack.
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.
- 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
- enterprise-grade SSD
- easy to add plugins including New Relic
- daily, weekly and monthly backups at no additional cost
- availability on multiple data centers
- a global support team to troubleshoot problems quickly
- dedicated servers available.