Learn how to design Daml applications to run on the Canton Network, with considerations for identity and access management, multi-domain applications, data management, and operational concerns for scale and performance.

Course-wide terminology and platform updates

This course was originally created using an earlier version of Canton. If you are using Canton 3, please keep the following updates in mind throughout the course:

• "Sync domain" (or "domain") is now called a "synchronizer". Any references to domains in the videos should be interpreted as synchronizers.

• Sequencers and mediators are independently operated components in Canton 3, rather than being presented as subcomponents of a single domain service. Some architectural descriptions in the videos reflect the earlier model.

• Configuration examples showing a single integrated domain service use the legacy configuration model. Canton 3 separates sequencer and mediator configuration.

• The JSON API is now provided natively by the participant node, rather than as a standalone proxy service.

Other than these terminology and platform updates, the concepts, workflows, and architectural principles presented in the course remain applicable.