Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

Table of Contents

...


Key Concepts


Project Management 

...

  1. set research investment and decision gateways for this process
  2. id ALL the functional, non-functional use cases in our current production solutions
  3. id any new critical requirements not met in current solutions that are a priority based on regulations, compliance, business value, risk
  4. review the candidate DLT solutions and their runtimes and integrations in detail 
  5. map to a candidate DLT platform and environment to see what platform provides and what we need to provide
  6. determine any delivery partners needed for the platform
  7. determine long-term support for any external services, products that we integrate
  8. design E2E deployment and operational support needs for the solution
  9. forecast viability, growth, risks of the external product or platform: community, costs, risks, quality, support etc
  10. perform the right evaluations:  POT, POC, POV


Learning Path


DAML learn

https://www.digitalasset.com/developers/learn


Daml Developer
Learn how to write Daml and build simple multi-party applications.

System Integration
Learn how to produce an application that depends on a Daml back-end for business logic and data persistence.

application-architect
System Architect
Learn about the different components and how they work together to produce a Daml solution


DAML basics certification ( free )

https://daml.talentlms.com/catalog/info/id:132?_ga=2.249195908.2087773921.1659974785-2111037199.1659974785



Why DAML?

https://daml.com/why-daml

...

Daml abstracts the event sourcing model employed by blockchains and distributed ledgers. Event sourcing means that the current state of the system can be computed from the log of past events. Instead of keeping a global event log, Daml provides each stakeholder a consistent view on a virtual shared event log, called the virtual shared ledger, while distributing data on a strict need-to-know basis under the hood. This creates a system in which each participant has a consistent view of the (virtual) global system state, consisting of exactly the data they are entitled to. The virtual shared ledger is described in Daml’s Ledger Model and implemented in the Daml smart contract language and associated Ledger API.

virtual-shared-ledger


The Ledger API is the primary API to interact with Daml smart contracts and the virtual shared ledger. It is a high-performance reactive gRPC-based streaming API. It allows applications to subscribe to events that they are permissioned to view, get their current state, or submit commands to write new events. As such, the Ledger API and smart contracts are the primary mechanisms for abstracting away concrete blockchains or databases to instead develop against a virtual shared ledger. Any node in a network that exposes Daml’s Ledger API—and thus gives access to the shared ledgers—is called a participant node as it allows participation in the network.

participant-nodes


To enable an infrastructure like a blockchain or database to run Daml applications, it needs a Daml Driver that allows a matching participant node to connect into the network. Daml Drivers do not store any data and are typically deployed per node of the underlying blockchain or database. There are already numerous drivers, both open source and commercial, available in the Daml ecosystem, with more under development. See https://daml.com for an overview.

...