Application Optimization – Caching and Block-level Deduplication
Application Optimization caching identifies which bytes are suitable for caching. It efficiently hashes, stores and then transports the bytes to the other edge device or node. The caching engine uses advanced rolling hash and indexing techniques to quickly and accurately locate blocks, and transports small block references in place of the original data. The Application Optimization engine takes care of the integrity and synchronization of the cache data, ensuring the correct data is always delivered quickly and efficiently to the branches or client. Unlike a traditional cache, the engine works across protocols for uploads and downloads. This means a file that is cached from an email attachment, will also be offloaded if the same file is uploaded or downloaded via HTTP or a file server.
Transcript
Hi, I’m Thomas. Welcome to the lightboard session on application optimization. By using caching or block-level deduplication, application optimization can significantly reduce the bandwidth required between your locations. When a client downloads a file from a server, we cache the data that has been transferred between two edge devices. If a second client requests the same file, instead of transferring the entire file again, we can use the cached data. We send a block reference to the data in the cache, which the client uses to look up the requested file, and the file is then sent to the client.
This approach works regardless of how the clients access the file. For example, the file might be initially transferred by email, and the second request might come through HTTP, FTP, or Samba. The cache stores byte sequences rather than the files themselves, so whenever we see the same byte sequence, we replace it with a reference to its stored address.
This method also ensures that if a file is updated on the server—where part of the file remains the same but some parts are changed—we would still transfer a block reference to the unchanged data and transfer only the modified parts. This way, the client always receives the most up-to-date version of the file, and the changes are also stored in the cache. By doing so, we drastically reduce the amount of data that needs to be transferred between edge devices.
Leave Complexity
Behind
To learn how Open Systems SASE Experience can benefit your organization, talk to a specialist today.
Contact Us