Skip to content

Hipsterdoom with Mongobingo

Felix Gessert does a postmortem of the failed Parse startup and product: “The AWS and MongoDB Infrastructure of Parse: Lessons Learned“.

Technical problem II: the real problem and bottleneck was not the API servers but almost always the shared MongoDB database cluster.

And that was with MongoRocks (Mongo on RocksDB) and replacing the initial app in Ruby with a Go implementation of said thing, with WriteConcern = 1, and other horrible presets. All in all, this is like the perfect nightmare of startup architecture decisions.

Felix closes pointing at his current project:

If this idea sounds interesting to you, have a look at Baqend. It is a high-performance BaaS that focuses on web performance through transparent caching and scalability through auto-sharding and polyglot persistence.

Bingo. Also, found the Hipster.

Published inPerformance

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *