Short answer: None.
Long Answer: Yes?
The whole philosophy of CouchDB is to think about everything that may be requested later, calculate it now (when it's convenient) and save the result in the index. All access to data from CouchdB comes from scanning one of these indices, which is very fast and tends to take about the same amount of time regardless of the amount of data (actually logarithmic time).
In addition, CouchDB does not consume much memory because it expects the operating system to cache its disk operations. The file system cache provides tremendous performance.
Finally, CouchDB supports all web standards for caching, so browsers and ISPs often cache it without doing anything special.
I believe my point is that for a high read load, CouchDB often does not need a cache. However, no, there is no built-in caching function. One of the reasons CouchDB uses HTTP is to allow people to use standard tools to solve their problems. Many people use web proxy caching in front of CouchDB in production.
Jason smith
source share