Shredded Storage in SharePoint 2013

It reduces the amount of data that is saved in the content DB & N/W traffic between WFE and DB server.

Reduce time to take back up of content DB.

SP 2010: When edit MS office: File Sync via SOAP over HTTP (MS-FSSHTTP) protocol locks portions of a file & download file to office document catch (ODC). When save to SharePoint: MS office save changes to ODC, then using MS-FSSHTTP to upload only differential to SharePoint server. Now SharePoint incorporate changes to document on SP server and entire document send to SQL server content DB. Because SharePoint unable to send to SQL server using MS-FSSHTTP.   SharePoint 2013 can now use MS-FSSHTTP to communicating with SQL servers.

Advantages of Shredded Storage:

A user can open a previously cached document, even if the SharePoint server is offline or not available.

Network utilization is reduced, which improves both performance and costs.

Users can start working with the document before it is completely downloaded.

When a user saves a document to SharePoint, the document is uploaded to the server in the background; thus it seems as if the save happens immediately.

In 2010 when you save same document simultaneously, SharePoint user multi master conflict used in co-authoring to merge the changes or resolve the conflict if modification done in same section.

But in 2013 no need to merge the changes. All changes goes to SQL server. It supports all types of files.

There is no concept of duplication. The new version of a file is not a complete copy of a file.