When automating tasks among many servers, information from one node may affect the configuration of another node or nodes. For example, if you configure DNS servers using Puppet, then you can have Puppet tell the rest of your nodes where all the DNS servers are located. This sharing of information is called catalog storage and searching in Puppet.
Catalog storage and searching was previously known as storeconfigs and enabled using the storeconfig option in puppet.conf. Storeconfigs was able to use SQLite, MySQL, and PostgreSQL; it is now deprecated in favor of
PuppetDB.
The current method of supporting exported resources is PuppetDB, which uses Java and PostgreSQL and can support hundreds to thousands of nodes with a single PuppetDB instance. Most scaling issues with PuppetDB can be solved by beefing up the PostgreSQL server, either adding a faster disk or more CPU, depending on the bottleneck.
We will begin our discussion of exported resources by configuring...