Skip to content

Instantly share code, notes, and snippets.

@marklit

marklit/rethinkdb-failure-reasons-according-to-hn.md

Forked from coffeemug/rethinkdb-failure-reasons-according-to-hn.md
Created January 18, 2017 10:48
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save marklit/5a8bd17bb164bfd577c64381134c0959 to your computer and use it in GitHub Desktop.
Save marklit/5a8bd17bb164bfd577c64381134c0959 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
rethinkdb-failure-reasons-according-to-hn.md 
- Inexplicable perversity of human nature.
- The clever machinations of MongoDB's marketing people.
- The AGPL license killed it.
- We spent too long development before monetizing.
- Bad performance.
- Numeric types limited to a 64-bit `float`.
- Great product, but didn't/couldn't translate to revenue.
- Bad business model.
- Failure in timezones/timestamp nuances.
- Document databases are a bad idea.
- Investment dried up due to noisy market.
- Did not solve problem companies using databases and having money
  need solved.
- NoSQL hype died out.
- No Java driver / automatic failover for too long.
- No cloud service.
- Trying to ship a cloud service.
- Failure of capitalism.
- MongoDB has done a way better job at SEO.
- Realtime technology was too early.
- Didn't build good sales/marketing teams.
- Bad name.
- The product was too good.
- Didn't have a Heroku addon.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment