Edgemesh aims to bring traditional server side technologies designed to improve user experience to the extreme edge of the network (the end user device). This includes intelligent caching, load balancing and security features.
Critical path: The critical path is defined as the user's direct access to content. Edgemesh will never get in the way of the critical path.
Asset Registration: The process of making a new asset available for edge caching. New assets are registered when a visitor of your site requests an asset and we can not serve it from local cache. This triggers a cache re-validation event for the asset, invalidating all stale copies globally.
Backplane: Edgemesh's back end service: Responsible for state management, cache invalidation, metric collection and making decisions for requests off the critical path.
Proxy: Edgemesh's client side proxy: Responsible for critical path decision making and implementation of Edgemesh's core features.
Client: Edgemesh's client: Responsible for instantiating Edgemesh and reporting performance metrics to the Backplane.
Organic: Edgemesh uses the visitors of your site as crawlers. Any time a user registers a new asset, an integrity check is run against all existing instances of that asset. If the check fails then the asset is removed from all caches globally.
Cache-Control Header: The Edgemesh Backplane reads the Cache-Control header of the registered asset and will automatically re-validate the asset according to the directives set on the header. The benefit here is that if the asset has not changed, caches are not thrashed by useless deletes and re-population. Edgemesh will intelligently back off on cache re-validation to help reduce bandwidth spend.
Portal or API: You can manually purge the cache through the Edgemesh Portal or API services. This method should not be necessary. It only exists to provide consumer piece of mind.