Recently Azure Blockchain workbench has released and seems its popular now. The Happy News is the Azure Blockchain Workbench 1.3.0 has released with Multi-member consortium support. Users can now upgrade their deployments to 1.3.0 or either users can create a new instance of workbench. To upgrade you can use upgrade script that released by Microsoft.
Once upgrade following enhancements will be added
It is fast and more reliable
Microsoft always check their telemetry to identify issues that affect to their customers, and decided to made some changes to make deploying Workbench more reliable. And faster.
Transaction reliability is much better
Microsoft has made a massive improvement for monitoring in version 1.1.0 and there are reliability improvements to the DLT (Distributed Ledger Technology) Watcher and DLT Consumer microservices. There may be some errors like, “It looks like something went wrong …”
In the release of 1.2.0 users had the feature to deploy Workbench and connect that deployment to an existing Ethereum-based network. And Microsoft was able to release a new standalone Ethereum PoA solution, which can be deployed across members within a consortium. These two updates brought up following features to Workbench.
There 3 configurations which you can deploy Workbench as following:
1. Single-Member System:
Workbench default configuration, in here Workbench is deployed in a blockchain. And it contains network with only one-member.
2. Multi-Member System Deployed in One Member’s Subscription:
The new feature deployed ‘multi-member PoA consortium solution’ is to deploy a blockchain network across several members. Here you can deploy Workbench in one member’s subscription. If anyone wants to go with the workbench uses the same subscription and one member’s Workbench deployment. This mechanism is useful to PoCs and initial pilot deployments.
3.Multi-Member System Deployed in One Shared Subscription:
This is more likely same the 2nd topology (Multi-Member System Deployed in One Member’s Subscription). The only difference is workbench will be deployed in a shared subscription. E.g The operator subscription for the consortium.
Much easier to Deploy with AAD
Once you are deploying a workbench according to Workbench deployment instructions it may be a huge task. Once you are trying to set up AAD and registering an app for the Workbench API as well. But Microsoft has released a PowerShell script to automate most of the AAD setup steps and outputs the parameters you need for Workbench deployment. Feel free to find it on GitHub.