The Duster Service provides template rendering using the LinkedIn Dust.js template engine. The Duster Service loads output templates for you, executes Dust across them and outputs markup like HTML and JSON. It allows you to build full web sites or custom APIs using a powerful template engine.
The Cloud CMS Application Server provides a library of * Dust Tags available out of the box. These are listed in more detail on the left-hand side menu.
Some Dust tags support caching so that the output of the tags can be cached and reused on subsequent requests.
For Dust tags that make remote API calls, for example, this can result in significant performance benefits.
The Cloud CMS Application Server automatically calculates the dependencies upon which the cached fragment was rendered. It retains knowledge about what was rendered (such as which content Node IDs) and what input arguments (such as locale, URI and user authentication information) were required to produce the fragment.
As such, fragment caching works innately with the Cloud CMS API and the Cloud CMS Notification Service to provide automatic cache invalidation. When content changes in Cloud CMS, the Cloud CMS Application Service hears about those changes and automatically clears the fragment cache.