Hello Daml community, I am currently porting contracts in solidity to daml, and I think that daml contract languages are better designed controlling access on read/write for states, and libraries are pretty much separated for focusing on state logics, which is what I like. Should I focus on building application logic on daml custom types and functions to use it as library, and then use one contract to manage read/write access? what is the best software design pattern for daml?
@hskang9 Welcome to the Daml community!
I’m afraid there’s no simple answser to your question, since there’s no one best design pattern for Daml. Daml and Canton are different from Solidity and EVM in many ways. For an application developer, arguably the most consequential differences are between Canton and EVM ledger models. To position yourself well for successfully developing Daml applications, I suggest you take the training courses that Digital Asset offers, starting with Daml Philosophy.
I would also suggest you take a look at the blog article titled Tokenization of RWAs on Canton Network vs EVM chains that aims to help developers with experience in Solidity to start coding in Daml. The article relates the concepts that are similar between Daml/Canton and Solidity/EVM, and explains some crucial differences.
1 Like