Key Points
References
| Reference_description_with_linked_URLs_______________________ | Notes______________________________________________________________ |
|---|---|
| https://daml.com/blog/engineering/public-blockchains-and-distributed-ledgers?utm_campaign=coschedule&utm_source=linkedin_company&utm_medium=Daml | |
| DAML-DigitalAssetSDK.pdf | |
Key Concepts
Like we learned with existing DLTs we've used we need to:
- set research investment and decision gateways for this process
- id ALL the functional, non-functional use cases in our current production solutions
- id any new critical requirements not met in current solutions that are a priority based on regulations, compliance, business value, risk
- review the candidate DLT solutions and their runtimes and integrations in detail
- map to a candidate DLT platform and environment to see what platform provides and what we need to provide
- determine any delivery partners needed for the platform
- determine long-term support for any external services, products that we integrate
- design E2E deployment and operational support needs for the solution
- forecast viability, growth, risks of the external product or platform: community, costs, risks, quality, support etc
- perform the right evaluations: POT, POC, POV
Questions
- what functional features are delivered in each environment?
- what is open-source ? how would that be supported?
- what is licensed ? what type of support levels are available?
- what operational features are provided compared to each of the supported native platforms?
- what level of architecture, product planning can we expect with the vendor? the community?
- what are keys for us in assessment if there is a value add?
Potential Value Opportunities
Potential Challenges
Candidate Solutions
DAML - language, tools, runtimes
can execute on Corda, Fabric, Besu
Step-by-step guide for Example
sample code block