Every database optimizes for different assumptions and situations. No single database will handle everything your app’s data needs, no matter how much database advocates want you to believe that. Mature applications use numerous databases for all the different things they need to do, from caching to logging to searching to reporting to graphing, and so on.
Comparing databases like MongoDB and PostgreSQL on the basis of performance miss the point that, categorically, those databases aren’t built for speed. Redis is built for speed. Select a database for durability and querying capabilities; select a cache for speed.
As app developers, we don’t know how to evaluate different databases. We just want to build apps. So we ask questions about performance, even though the greatest performance hit any database will give you is when it drops dead at 3am and you have to fix it. Until then, virtually every database will be fast enough.
The reality is that most systems have pretty similar needs, but no single database can handle all of them. That’s the philosophy behind Orchestrate: let’s take the best-in-class database solutions for problems every app developer has, and tie them together behind a sensible API. Then we can leverage existing open standards and open technology to deliver features, rather than having to reinvent the wheel every time we want to give our users a new feature.
Rather than build the One True Database, we’re using tried and true databases to deliver the tools every app developer needs. Sign up and let us know what you think of that approach.