Skip to content

DOCS-580 FAQ: database caching #371

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 6, 2012
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions source/faq/fundamentals.txt
Original file line number Diff line number Diff line change
Expand Up @@ -135,6 +135,21 @@ in RAM, MongoDB serves all queries from memory.
MongoDB does not implement a query cache: MongoDB serves all queries
directly from the indexes and/or data files.

Does MongoDB require a separate caching layer for application-level caching?
----------------------------------------------------------------------------

No. In MongoDB, a document's representation in the database is similar
to its representation in application memory. This means the database
already stores the usable form of data, making the data usable in both
the persistent store and in the application cache. This eliminates the
need for a separate caching layer in the application.

This differs from relational databases, where caching data is more
expensive. Relational databases must transform data into object
representations that applications can read and must store the
transformed data in a separate cache. If joins are required that adds to
the overhead.

What language is MongoDB written in?
------------------------------------

Expand Down