AWS Blockchain versus AWS for Blockchain
Easy at first is not easy at scale. What you may not foresee when picking a way to deploy a blockchain network.
When you are hitting production you may face with the option to pick a cloud provider or else do things yourself.
Usually, people are looking for the easiest way that provides the most control. So looking to Amazon Web Services seems like a good idea at first.
AWS Blockchain
Amazon announced their Blockchain templates a while ago, and people rely on them to deploy (in a, mostly, easy way) a started Hyperledger Fabric network.
However, there are quite some downsides of picking that way to deploy.
- For instance, the computing layer and the blockchain components are completely coupled. That means that you get stuck with AWS, forever. That is a problem in general with higher-level services like PaaS, where you need a third party to actually have freedom.
- A template gives you the starting point, but what about operations and growing the network? Like adding new participants, monitoring its health, installing chaincodes or creating channels? That’s all on your side. You need quite some knowledge that you may not foresee when just getting started.
- Integrating with organizations outside of yours will become a general pain. What if another organization runs in Azure? They will need to learn how to deploy there and that may create sufficient frictions to stop them from getting into the network.
- Finally, since it’s a template-based deployment, not only changes go on you, but also updates, security checks, and so on.
These are red flags you need to spot before putting your eggs into a single basket. A network is not something static, it grows, and that’s what brings the value. More members, more data, more value.
But AWS’s infrastructure is great… Yea, use AWS for Blockchain!
That’s right! Using managed infrastructure is the most agile way to start and grow a solution. You don’t need to worry about the physical infrastructure and start in minutes.
Here’s where you can use AWS for Blockchain instead of AWS Blockchain.
Out of the experience in WorldSibu we created Forma, a multi-cloud infrastructure automation platform for Hyperledger Fabric (and soon other ledgers!). It decouples the computing layer from the blockchain components layer, and as it spans through multiple cloud providers, the whole network can be coordinated without centralizing all the infrastructure.
You may think that it sounds like a “Blockchain as a Service” however unlike services that centralize the infrastructure, Forma remotely connects to your own cloud service account or bare-metal data center. This means that you keep the confidentiality of your data wherever you want (Europe, Asia, Latin America, US, your own data center) and can apply compliance policies as required.
So, if you like, continue to use AWS! But don’t lock your network up into a single cloud provider. Forma also supports Microsoft Azure, IBM Cloud, Google Cloud Platform, Digital Ocean, and bare-metal Kubernetes.
Another advantage of this model is that any task such as creating channels (ledgers), installing or upgrading smart contracts, and even creating new users in the Certificate Authorities is achieved by simply filling a web form, even in complex multi-cloud multi-company networks.
As decision-makers, it’s always important to consider the long term over the short term. You need to future-proof your solution, maximize the chances for growth and success, and reduce frictions as much as possible.
In this cloud-first world, options that allow you to use cloud providers instead of getting used by them should be part of your toolbox as much as possible.
Interested in knowing more? Read more here and check this comparison table versus cloud provider’s blockchain offerings.
Want to get a demo or a free trial? Get one here:
- 👉Forma Trial.
