Design Content Type Syndication
Earlier in this lesson, we proposed that many organizations will require only one term store, and therefore only one Managed Metadata Service application.
However, when you factor content type syndication into your design, the equation can change. Each Managed Metadata Service application can publish content
types from only one content type hub. If you want content types from multiple site collections to be published, you must create additional Managed Metadata
Service applications, each with a unique content type hub. Web applications in the farm can connect to each of the Managed Metadata Service applications
from which they require content types.
In such a model, additional Managed Metadata Service applications are providing only content type syndication functionality. Managing unique term stores is
not inherently required, so the additional term stores can remain empty.
Alternately, you can create a single site collection that serves as the content type hub for the enterprise, and each organization that wants to define
content types can do so within that site collection. The site collection is, in effect, dedicated to content type publishing, and does not contain any
user-facing pages, lists, or libraries.
The figure above shows a Managed Metadata Service application that provides enterprise-wide taxonomy and folksonomy, as well as content types that are
managed in a centrally defined, dedicated site collection. A second Managed Metadata Service application is used to publish content types that are managed
by the legal department, but contains no terms. A third Managed Metadata Service application contains terms that the R&D department wants to isolate
from the rest of the organization. And a fourth Managed Metadata Service application contains terms and content types that are published to a farm that is
shared with a partner organization.