... | ... | @@ -65,5 +65,10 @@ The pristine version of Soledad used to store all data as JSON documents, which |
|
|
Starting with **0.10.0**, Soledad now has a proper BLOB infrastructure that decouples payloads from metadata both in storage and in the synchronization process. The first use case was mail delivery, and we implemented an API so the MX component now hands Soledad Server the responsibility of packing and storing incoming messages as public-key-encrypted data. Metadata is synchronized using the usual sync mechanism, while BLOBs are synchronized in parallel and on-demand. This makes it feasible to have much quicker feedback of incoming messages and load their content and attachments on demand, as is done in most implementations of IMAP clients.
|
|
|
|
|
|
## Client-side transfer/crypto pipeline optimization.
|
|
|
|
|
|
The following is a graph showing the time improvement between legacy (as baseline) and blobs implementations with different features:
|
|
|
|
|
|
![legacy-vs-blobs](/uploads/89dbd75715d466478cad7b8e6745de9a/legacy-vs-blobs.png)
|
|
|
|
|
|
## Server-side backend storage optimization.
|
|
|
## Server scalability. |
|
|
\ No newline at end of file |