Chapter 17

Document Database Products

In This Chapter

arrow Replacing memcache

arrow Providing a familiar developer experience

arrow Delivering an end-to-end document platform

arrow Creating a web application back end

If you’ve decided that a document-orientated, schema-free, tree-structured approach is for you, then you have several choices because many great and varied document NoSQL databases are available. But the question, of course, is which one to use?

Perhaps your organization requires the ability to scale out for high-speed writes. Maybe, instead, you have only a few documents with high-value data. Perhaps you’re looking for a relational database that your developers are familiar with.

Because the fundamental designs of databases differ, there’s no one-size-fits-all approach. These designs are neither wrong nor right; they’re just different because each database is designed for a different use. They become “wrong” only if they’re applied to the wrong type of problem.

In this chapter, I explain how to make the choice that best suits your needs.

Providing a Memcache Replacement

Memcache is an ...

Get NoSQL For Dummies now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.