The Polkadot Cloud
This is a repost from the Polkadot forum, where I describe my vision of the Polkadot Cloud.
I think it's time to open a thread dedicated to the ideas which have been spreading like wildfire (very much by intention) around the Polkadot Hub and Polkadot Cloud.
First, before we even get started, it is important to note that this is just a discussion of ideas. Nothing here is locked in yet, official, or anything like that. The point of these conversations is to get community alignment of ideas, terminology, vision, and direction.
The phrase I have been using is that Polkadot is like a bunch of cats in a room, totally doing their own thing. We need a laser pointer for us all to focus on a long-term vision, and to move together towards that goal.
Such a vision should allow us to:
- make better decisions as a community
- better represent Polkadot outside of our community
- ensure that we are building things that are relevant for our needs
What is also important is that our vision is not made up. It must be something we can actually achieve, and that we have ideas to support.
What is Polkadot?
Polkadot is not a blockchain. Polkadot of course, has a blockchain, and a token, but the meaning of Polkadot extends far beyond that.
Polkadot is a vision toward a world with less trust and more truth.
This is the friendly way to tell people that we are trying to build and innovate with Web3 principles.
I think if you look at all that Polkadot has done in the past, is doing now, and will do into the future, this single vision will permeate every decision and action we take.
This vision will likely never change, nor should it. I think Polkadot is defined by the journey we take toward this vision.
Polkadot has a mission, which describes the direction we go in achieving that vision. Our mission can change, but practically, changes in our mission should only occur over long periods of time. Only when what is needed to reach our vision changes, or we have achieved our current mission.
We can describe Polkadot's mission up until now and into the near future:
Polkadot’s mission is to provide a scalable, secure, and resilient platform for Web3 applications and services.
An image to put in your mind is:
That is to say, Amazon Web Services has fundamentally changed the internet today by making it cheap, easy, and scalable to launch Web2 applications and services into the cloud.
Polkadot's current mission is to do the same thing, but for Web3 services. We believe this is the way that the Polkadot ecosystem can currently bring this vision of a world with less trust and more truth to the world, and while we acknowledge achieving this vision requires more than just technology, we think it is the first primitive the world needs to get started.
So what does it mean to have a vision towards less trust and more truth?
To answer this, we must ask "What is Web3?".
What is Web3?
Web3 is a fundamental shift of removing trust from Web2, the technology stack that we currently use to power the internet.
In my recent presentation, I represented this as a difference in resilience.
But in fact, there are other principles of Web3 we should not forget:
As quoted by Gav:
Driving Factors and Web3 Maxims
- Resilience
- Generality
- Performance
- Coherency
- Accessibility
I would also like to include the 5 pillars of open blockchains from Andreas Antonopoulos, which was certainly the predecessor to Web3 ideologies:
- Open
- Public
- Borderless
- Neutral
- Censorship Resistant
This post is probably not best suited to be the introduction into the principles and philosophies of Web3.
If there are nice posts which consolidate and teach the ideas of Web3 which can be linked here, please feel free to post them in this thread. Otherwise, perhaps look at the old youtube videos of Gav or other Web3 leaders about their vision of the space.
Polkadot's Products
So we have established our vision, and have a clear mission to bring technologies into the world which can power Web3 applications and services.
How does this actually manifest into products?
Well my perspective is that Polkadot has always been building toward two products, which attempt to satisfy this mission:
- The Polkadot Cloud
- The Polkadot Hub
NOTE: It is important at this point to not get too attached to these specific names. Many resonate with the Polkadot Cloud, but some have opinions about the "Polkadot Hub", and this is the time to discuss those opinions and come to a consensus. I personally prefer these two names, and would be happy to have those discussions with anyone here in this thread.
Unfortunately the history of developing the Polkadot, we had not clearly defined these two products. But it does not change the fact that if we think about what we have been building so far and the vision we are going toward, we have ALWAYS been building these two products.
So, what is the Polkadot Cloud and the Polkadot Hub?
The Polkadot Cloud
The Polkadot Cloud is a secure, scalable, and resilient platform for Web3 applications and services.
The Polkadot Cloud is our current mission.
If you were to make a sales pitch for the Polkadot Cloud, it might look something like this:
The Polkadot Cloud is a platform for Web3 applications and services.
On the Polkadot Cloud, we provide services with high throughput, native interoperability, and shared security. Our cloud platform is elastic, dynamic and multi-core.
With over 100 execution cores we are able to achieve 150,000 transactions per second across the Cloud, and over 150 MB/s data availability throughput!
The Polkadot Cloud offers a number of different Web3 Services such as:
- Cloud Execution Service
- Settlement / Finality Service
- Data Availability Service
- Object Storage Service
- Blockchain Hosting Service
- and more!
All of these services work together seamlessly to create an all-in-one platform for deploying your app. We provide everything you need, so you can focus on what you are building.
Using the Polkadot Cloud, you are able to deploy any kind of Web3 application or service cheap, easy, and at scale.
Note here that the Polkadot Cloud represents all that we have accomplished so far, and even looks into what we want to do in the future.
It also breaks down the various features of Polkadot into separate services that are offered and bundled by the Cloud. And this better represents what you can actually do, rather than what we have currently built.
There are teams already experimenting with using our individual services like data availability or cloud execution to secure rollups on other ecosystems. We could be part of every "modular blockchain" story. It's just that we have been focused on building an all-in-one solution.
History of the Polkadot Cloud
With this framing of the Polkadot Cloud, I think we are able to actually look back at history, and define a clear story of what we have been building so far.
Not to make up history, but to re-frame what we've done.
- Polkadot Cloud - Genesis: May 2020
- Polkadot Cloud - Milestone I (Parachains): November 2021
- First Cloud Services Deploy: December 2021
- Polkadot Cloud - Milestone II (Elastic): October 2024
- Polkadot Cloud - Milestone III (JAM): TBD
So really, the initial Polkadot launch was really around creating an all-in-one blockchain hosting service for other blockchains on the Polkadot Cloud.
Initially that blockchain hosting service was very simple in how it created, allocated, and used blockspace.
Our work since the launch of Polkadot have been to make our hosting service more agile, elastic, and flexible. This is what we previously called "Polkadot 2.0", but it really isn't a new product at all! It is an iteration of the Polkadot Cloud vision.
Just like JAM is also not a brand new idea, even though the architecture of the Polkadot Cloud will change significantly from it. It is yet another iteration on the mission to create the best platform for Web3 applications and services.
With the third milestone of the Polkadot Cloud (codename JAM), we are looking to extend functionality of our Web3 Cloud platform to support even applications and services which are NOT blockchains.
I think this kind of positioning helps explain to the world what the heck is going on with things like JAM, which we have really struggled to explain in respect to the existing Polkadot Cloud.
And certainly there will be milestone 4, 5, 6, etc... The development and improvement of the Polkadot Cloud will always continue. It is wrong to look at the development of Polkadot as "building new products". The product is the same, it is just iteratively (or sometimes radically) getting better.
The question you need to ask when digging into technical development, is:
"How does this improve the Polkadot Cloud?".
This is what we need to be communicating.
Comparisons to Web2 Clouds
I think that this vision of the Polkadot Cloud allows us to evaluate what we have been building, and where we should be building toward. Thankfully, we have large businesses like Amazon, Google, and Microsoft who have all built Web2 clouds, of which I argue we are not that different from an architectural standpoint.
For example, look at the service offerings for Amazon:
- Amazon EC2
- EC2 = Elastic Compute Cloud
- "Amazon EC2 is AWS's service that provides secure, scalable computing capacity in the cloud."
- "Reliable and scalable infrastructure on-demand, with 99.99% availability SLA"
- "purchase model to help you best match the needs of your workload"
- Amazon S3
- S3 = Simple Storage Service
- "Amazon S3 is an object storage service offering industry-leading scalability, data availability, security, and performance."
- Benefits:
- Scalability
- Durability and availability
- Security and data protection
- Lowest price and highest performance
- AWS Lambda
- "Run code without thinking about servers or clusters"
- "AWS Lambda is a serverless computing service that runs your code in response to events without requiring provisioning or management of servers. It automatically scales compute resources and you pay only for the compute time used. The main benefits are no server management, automatic scaling, pay-per-use billing, and performance optimization options."
Doesn't this draw a lot of parallels to:
- Our execution service
- Our data availability service
- The proposed "CorePlay" service
Take a look at the Google Cloud landing page. Couldn't you see this structure and style being an effective way to explain and sell the Polkadot Cloud?
Imagine all that we can learn about creating a better Web3 cloud for the world by really framing ourselves as a product architected similar to the traditional cloud services we want to replace.