StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Product

  • Stacks
  • Tools
  • Companies
  • Feed

Company

  • About
  • Blog
  • Contact

Legal

  • Privacy Policy
  • Terms of Service

© 2025 StackShare. All rights reserved.

API StatusChangelog
  1. Home
  2. Companies
  3. ReadMe.io
ReadMe.io logo

ReadMe.io

Verified

Collaborative Developer Hubs

san franciscoreadme.io
30
Tools
1
Decisions
649
Followers

Tech Stack

Application & Data

7 tools

AngularJS logo
AngularJS
MongoDB logo
MongoDB
Node.js logo
Node.js
ExpressJS logo
ExpressJS
Mongoose logo
Mongoose
CloudFlare logo
CloudFlare
JavaScript logo
JavaScript

Utilities

5 tools

Baremetrics logo
Baremetrics
Slack logo
Slack
Heap logo
Heap
Stripe logo
Stripe
Elasticsearch logo
Elasticsearch

Business Tools

1 tool

Clearbit logo
Clearbit

Team Members

Gregory Koberger
Gregory KobergerFounder
Justina Nguyen
Justina Nguyen

Engineering Blog

Stack Decisions

Gregory Koberger
Gregory Koberger

Oct 3, 2018

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.

196k views196k
Comments