Does the global synchronizer essentially eliminate the need to use other backends such as a permissioned blockchain, or distributed database for domain synchronization?
Yes it does. You can link a Participant node directly to the global synchronizer.
Some caveats:
- The global synchronizer works only for Daml 3.x, which is in early access at the moment.
- You need to run the Global Synchronizer’s “Validator” app via your Daml 3.x Participant node in order to ask the Super Validators to track a traffic balance for your node.
1 Like
I’ll add to Wayne’s answer that there are still reasons to use a private synchronizer (centralized or distributed). So the global synchronizer allows eliminates the need to user other backends, but not the option to use them.
Thanks for the follow-up. I was thinking there may be use-cases for a hybrid approach: using a combination of both a private shared domain and the global synchronizer. Nice to have the flexibility.
Yes, the system is designed with hybrid use cases as the priority.