Setting up caching nodes and microservice clients for Content Delivery embedded caching
Embedded caching on the server is handled through the Content Deployer and through the (Session-enabled) Content Service. Both services contain Ignite libraries and appear as Ignite nodes in an Ignite cluster. By default, both Ignite nodes act as servers joined in a cluster, storing cached entities and performing computational tasks. You can change this default setup in several ways, according to your preferences.