Fourth installment on replication technologies: Microsoft Sync Framework 2.1 (retired in 2016).

I’m including the Microsoft Sync Framework because this article includes a good detailed description of how its replication strategy works with a fair bit of architectural detail. It maps reasonably well to the SDS Confidential Storage Model conceptual architecture: https://docs.microsoft.com/en-us/previous-versions/mt763482(v=msdn.10)?redirectedfrom=MSDN

I believe Ray Ozzie and his brother Jack drove the Sync Framework after they joined Microsoft as part of the Groove Networks acquisition.

Best regards,

Michael

Here’s the third installment on different replication approaches: Microsoft Active Directory Replication Model.

The AD Replication Model is interesting because it uses a different approach to track adds/deletes/updates: one based on Update Sequence Numbers and Tombstoning.

For the full story on AD Replication Model, check out this article:

How the Active Directory Replication Model Works

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc772726(v=ws.10)?redirectedfrom=MSDN#determining-changes-to-replicate-update-sequence-numbers

Best regards,

Michael

[Resending the Syntergy Replicator replication pipeline documents to sds-wg@dif.groups.io]

Here’s the replication that diagram I created several years ago at Syntergy as their solution architect …at a high level, it’s actually only 3 components:

The source and target servers could be clients and/servers or intermediary router.  For more details, see page 17 and onwards in the attached whitepaper.

“More news at 11…”

As a follow-up to the background information I’ve sent out regarding replication technologies, I’ve been working on a white paper over the last few days entitled:

Secure Data Storage Working Group (sds-wg) Confidential Storage (CS): Functional Architecture Reference Models (CS-FARMs)

It starts with the SDS Layers diagram…

..and uses the following framework to describe a very detailed set of architecture variations for a secure storage/confidential storage solution architecture:

“More news at 11...”

Best regards,

Michael Herman

Self-Sovereign Blockchain Architect

Trusted Digital Web

Hyperonomy Digital Identity Lab

Parallelspace Corporation

Fourth installment on replication technologies: Microsoft Sync Framework 2.1 (retired in 2016).

I’m including the Microsoft Sync Framework because this article includes a good detailed description of how its replication strategy works with a fair bit of architectural detail. It maps reasonably well to the SDS Confidential Storage Model conceptual architecture: https://docs.microsoft.com/en-us/previous-versions/mt763482(v=msdn.10)?redirectedfrom=MSDN

I believe Ray Ozzie and his brother Jack drove the Sync Framework after they joined Microsoft as part of the Groove Networks acquisition.

Best regards,

Michael

Here’s the third installment on different replication approaches: Microsoft Active Directory Replication Model.

The AD Replication Model is interesting because it uses a different approach to track adds/deletes/updates: one based on Update Sequence Numbers and Tombstoning.

For the full story on AD Replication Model, check out this article:

How the Active Directory Replication Model Works

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc772726(v=ws.10)?redirectedfrom=MSDN#determining-changes-to-replicate-update-sequence-numbers

Best regards,

Michael

[Resending the Syntergy Replicator replication pipeline documents to sds-wg@dif.groups.io]

Here’s the replication that diagram I created several years ago at Syntergy as their solution architect …at a high level, it’s actually only 3 components:

The source and target servers could be clients and/servers or intermediary router.  For more details, see page 17 and onwards in the attached whitepaper.

“More news at 11…”