Philosophy

Design Philosophy

  • Databases are specializing - the "one size fits all" approach no longer applies.
  • By reducing transactional semantics the db provides, one can still solve an interesting set of problems where performance is very important, and horizontal scaling then becomes easier.
  • The (JSON) document data model is easy to code to, easy to manage (schemaless), and yields excellent performance by grouping relevant data together internally.
  • A non-relational approach is the best path to database solutions which scale horizontally to many machines.
  • While there is an opportunity to relax certain capabilities for better performance, there is also a need for deeper functionality than that provided by pure key/value stores.
  • Database technology should run anywhere, being available both for running on your own servers or VMs, and also as a cloud pay-for-what-you-use service.


Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

PLEASE POST QUESTIONS IN THE USER GROUPS FORUM. Post non-question comments and helpful hints here.

blog comments powered by Disqus