At Silença Tech we often get asked by startups what platform is optimal to design their distributed software. I want to share with you what logic we follow and driven by to give the best response to our . Of course, tech specs should be taken into consideration, and also it always depends on the specificity of software etc. However, I’d like to elaborate on the most common use cases.
First and foremost, what needs to be determined is the level of access granted to participants. In other words, whether a network is going to be public or private. Even though about 90% of networks are public, private network is the best choice for a certain type of applications.
If your venture needs public , that means that user trust is essential, and 100% of transactions will be transparent, and most probably you need utility (s).
Among public blockchains, I would outline , , and . They allow smart-contracts, what makes it a good fit to build sophisticated DApps. has an exceptional infrastructure, advanced functionality, and much higher bandwidth than . Besides, is hyped up and that makes it a popular choice, giving certain high-tech startups to utilize cutting edge technologies. Meanwhile, has low transaction cost, its internal language is commonly known Java, and many other advantages over .
And yet, to the most startups, we recommend Public .
The reasons are rather pragmatic. MVP can be developed easily and deployed pretty fast. Currently, there are plenty of Solidity developers on the market, much more in comparison with any other (Solidity is an internal language). There is a huge community actively present online, that means answers to solve your issues can be found quicker. Basically, Google has more articles to address numerous problems every MVP inevitably goes through at some point).
That is why DApp rating looks like on post`s image.
Published at Sat, 13 Apr 2019 15:08:42 +0000
