Caching in the Web3 Platform

There are several other concepts around the APIs that are important to understand when developing applications. The first of these is how caching is handled. The Web3 platform has a separate cache service. This cache service is never used directly by client applications, but is used by the Topic Map and Schema services. The cache service stores the representations of Web3 resource so that they can be quickly returned when requested. The cache entry for a given resource (e.g. a topic, an association) is cleared when that construct is updated via the service.

Updates to Web3 resources result in a message being posted to a persistent message queue.