Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

This page contains information on the cache definitions within core.
Each cache definition found within core will be under its own heading and will include a description of the cache.
As well as the name and description the following information will also be details:

Since
When this cache definition was first introduced into Moodle.
Component/Area
The code component this cache belongs to and the area (unique simple name) given to it.
Growth
Will state if this cache is expected to be of fixed size, or can be expected to grow as the site data grows. Perhaps some information on how the cache will grow.
Who
Which users can expect to benefit from the cache.
Priority
An indication of the anticipated cache use on a site. A value between 1 and 5. If the cache is of fixed size and is accessed expected to be utilised on every page it will be given a 5 for priority as it can be expected that assigning that cache to the fastest backend available would be the good idea. In contrast a priority of 1 would be given to a cache that is expected to grow quickly, is only accessed on specific pages, and only applies to some users (e.g. teachers, or the admin). This cache should be the least of your concerns when deciding upon how to implement caching on your site.

Application caches

Application caches are shared caches.

Accumulated information about modules and sections for each course

Since
Component/Area
core, coursemodinfo
Growth
Who
Priority

Calendar subscriptions

Since
Component/Area
core, calendar_subscriptions
Growth
Who
Priority

Concept linking [mod_glossary]

Since
Component/Area
mod_glossary, concepts
Growth
Who
Priority

Config settings

Since
Component/Area
core, config
Growth
Who
Priority

Course categories tree

Since
Component/Area
core, coursecattree
Growth
Who
Priority

Course group information

Since
Component/Area
core, groupdata
Growth
Who
Priority

Database meta information

Since
Component/Area
core, databasemeta
Growth
Who
Priority

Event invalidation

Since
Component/Area
core, eventinvalidation
Growth
Who
Priority

Event observers

Since
Component/Area
core, observers
Growth
Who
Priority

External badges for particular user

Since
Component/Area
core, externalbadges
Growth
Who
Priority

Grade items cached for evaluating conditional availability [availability_grade, items]

Since
Component/Area
availability_grade, items
Growth
Who
Priority

HTML Purifier - cleaned content

Since
Component/Area
core, htmlpurifier
Growth
Who
Priority

Language string cache

The language string cache is one of the most essential caches within Moodle. It caches each and every language file used within Moodle. Its of fixed size as there are a finite number of languages and language files and as it is accessed one pretty much every page within Moodle. This is a prime cache to configure, map it to the fastest backend you've got available.

Since
Moodle 2.4
Component/Area
core, string
Growth
fixed size, each language string file is cached here, its size will be fixed but will be determined by the number of languages available on your site.
Who
everyone, on every browsable page within Moodle.
Priority
5

List of available languages

Since
Component/Area
core, langmenu
Growth
Who
Priority

List of course contacts

Since
Component/Area
core, coursecontacts
Growth
Who
Priority

Plugin info manager

Since
Component/Area
core, plugin_manager
Growth
Who
Priority

Question definitions

Since
Component/Area
core, questiondata
Growth
Who
Priority

User grades cached for evaluating conditional availability

Since
Component/Area
core, gradecondition
Growth
Who
Priority

User grades cached for evaluating conditional availability [availability_grade, scores]

Since
Component/Area
availability, scores
Growth
Who
Priority

YUI Module definitions

Since
Component/Area
core, yuimodules
Growth
Who
Priority

Session caches

Data cached here belongs to the user browsing the site.

Course categories lists for particular user

Since
Component/Area
core, coursecat
Growth
Who
Priority

Data used to persist user selections throughout Moodle

Since
Component/Area
core, userselections
Growth
Who
Priority

Folder name cache [repository_skydrive]

Since
Component/Area
repository_skydrive, foldername
Growth
Who
Priority

Request caches

Caches here last only for the life time of the request and are only available to the browsing user.

Course categories records

Since
Component/Area
core, coursecatrecords
Growth
Who
Priority

Helper caching [tool_uploadcourse]

Since
Component/Area
tool_uploadcourse, helper
Growth
Who
Priority

Repositories instances data

Since
Component/Area
core, repositories
Growth
Who
Priority