#Appchains chatter is picking up lately and Avalanche Subnets have a lot to offer.
Avalanche is essentially the closest decentralized #web3 equivalent to Amazon Web Services due to a few very specific properties.
The benefits of web3 + the UX of web2 = ♥️
A short ELI12 👇
Avalanche is essentially the closest decentralized #web3 equivalent to Amazon Web Services due to a few very specific properties.
The benefits of web3 + the UX of web2 = ♥️
A short ELI12 👇
A blockchain is to web3 as a server is to web2. In web2 every webpage and application has its own server or a geo-balanced network of servers.
A blockchain shares its limited resources between an unlimited number of dapps whose users fight for concurrency through gas fees.
A blockchain shares its limited resources between an unlimited number of dapps whose users fight for concurrency through gas fees.
A network like Avalanche offers those dapps to isolate an entire chain or even a network of chains for their users. Same as AWS offers servers or networks of servers in web2 instead of having 1 giant server trying to host all the world's apps.
Avalanche Subnets are a horizontally scalable solution for Appchains (possibly >300k chains capacity) as the protocol has virtually no limitation on its number of validators.
Combined with the >1s transaction finality, and the design flexibility among other properties of Avalanche, they could solve several problems both for apps transitioning from web2 and native web3 builders alike.
How can #Avalanche help?
>Concurrency<
Subnets allow apps to isolate an entire blockchain capacity or even launch multiple subnets to serve different regions if they face a growing demand for blockspace.
>Concurrency<
Subnets allow apps to isolate an entire blockchain capacity or even launch multiple subnets to serve different regions if they face a growing demand for blockspace.
>High fees< (congestion)
High fees are a product of growing demand on a congested network. The lack of concurrency and the ability to scale horizontally gives builders all the tools they need to ensure their users have a good experience.
High fees are a product of growing demand on a congested network. The lack of concurrency and the ability to scale horizontally gives builders all the tools they need to ensure their users have a good experience.
>Slow UIs/Weak Performance<
In web2, we are used to lightning-fast interactions with application UIs. Going from low hundreds milliseconds to 120 seconds does not justify the benefits of web3 for many use cases, especially in applications that rely heavily on latency.
In web2, we are used to lightning-fast interactions with application UIs. Going from low hundreds milliseconds to 120 seconds does not justify the benefits of web3 for many use cases, especially in applications that rely heavily on latency.
Avalanche offers lighting fast transactions measured by time to finality, with an average latency of 800ms.
>Scalability<
Subnets are a blank slate that lets you implement any scalability solution. One can spin multiple subnets as sidechains, L2s, L3s a combination of them. The flexibility of their design allows builders to stay on edge with innovation.
Subnets are a blank slate that lets you implement any scalability solution. One can spin multiple subnets as sidechains, L2s, L3s a combination of them. The flexibility of their design allows builders to stay on edge with innovation.
>Complexity to launch<
Launching a blockchain is a complex process you can’t learn from tutorials on the internet. It usually goes through several testing phases that take months or even years of development.
Launching a blockchain is a complex process you can’t learn from tutorials on the internet. It usually goes through several testing phases that take months or even years of development.
Launching a subnet is a several steps process that anyone with basic Linux knowledge can follow through in several minutes. That alone can save thousands of hours of work for a full team of engineers and administration.
>Design Limitations<
Existing BaaS solutions are broadly limiting and mostly tailored for private blockchains.
Builders have to make significant tradeoffs in their design decisions in functionality, economic model, ownership, etc.
Existing BaaS solutions are broadly limiting and mostly tailored for private blockchains.
Builders have to make significant tradeoffs in their design decisions in functionality, economic model, ownership, etc.
Subnets allow builders to set their requirements for validators, their gas fee structures, virtual machines, whether to be permissioned or permissionless, their feature sets, security budget, utility, and literally every parameter.
That said, I'm excited for the next wave of web3 adoption as the tech moves onto levels that could allow it.
Avalanche and Cosmos both made big breakthroughs in the area based on different techs resulting in different sets of properties = more flexibility = more adoption.
Avalanche and Cosmos both made big breakthroughs in the area based on different techs resulting in different sets of properties = more flexibility = more adoption.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
