Everyone in the enterprise world already has a blockchain strategy. If they don’t have one now, they risk the chance of staying behind or simply missing an opportunity. For the last few years, the benefits and correlated risks of fully adopting blockchain technology have been estimated, analyzed, and discussed at large. One thing is clear – despite the potential for a big upside, embracing a newly developed technology presents numerous risks that shouldn’t be underestimated. Blindly introducing new technology stack into an already working production environment means exposing that environment to potentially dangerous security breaches, hacks and data loss.
So, where we are now? Most blockchain protocols claim some level or maturity … but are they, in fact, sufficiently mature? Are they ready for full on-premise deployment in large-scale enterprises? Will CIOs and other business executives enjoy the same comfort as that of the tooling they already have? Let’s review what it takes to move a blockchain protocol from open source to enterprise.
It’s no surprise that the largest cloud providers are also the largest drivers of the Blockchain as a Service (BaaS) model. Let’s call them Tier 1 BaaS providers. They have already established themselves as market leaders with large customer bases. Offering various cloud services and expanding to blockchain seemed to be a logical and evolutional step.
Microsoft is one of the largest players in the BaaS space. So far, it has focused primarily on Ethereum but also offers services for running R3’s Corda and Hyperledger Fabric networks. It has dedicated many resources to building the Azure Blockchain Workbench and Azure Blockchain Service. Microsoft’s team is also a key founder and an active participant in the Ethereum Enterprise Alliance (EEA) and Token Taxonomy Initiative (TTI). In addition, it has recently joined the Hyperledger family, for which it will contribute to the code...