The document discusses key considerations for enterprise blockchain implementations, including selecting a blockchain platform, runtime, and complementary technology stacks. It analyzes popular permissioned blockchain platforms like Hyperledger Fabric, Sawtooth, and Corda and cloud services from Azure, AWS, IBM and others. It also reviews relevant technology stacks for integration, testing, data storage, access and security. The conclusion recommends starting small and iterating when establishing a blockchain strategy to address challenges of real-world solutions.
10. Hyperledger Fabric
Key Capabilities
• Based on the open source Hyperledger implementation
• Supports smart contracts via chaincode and containers(Java, Go, NodeJS)
• Identity and privacy based protocols
• Networks can be segmented in channels
• Advanced toolset with products like Composer
Strengths
• Integration with external systems
• Solutions portfolio
• Partner community
Weaknesses
• Smart contract model
• Toolset for app lifecyle management
• Lack of support for public blockchain topologies
11. Hyperledger Sawtooth
Key Capabilities
• Based on the open source Hyperledger implementation
• Supports for EVM smart contracts
• Native supply-chain like tracking capabilities
• PoET consensus model
• Native support for Docker containers
Strengths
• Simple programming model
• Interoperability with Ethereum
• Flexible network topology using validators
Weaknesses
• Lack of developer community
• Limited toolset
• Integration with external systems
12. Quorum
Key Capabilities
• Permissioned version of the Ethereum blockchain
• Various consensus mechanisms(Raft and Istanbul BFT implementations)
• Privacy protocols based on zk-SNARKs
• Support for private smart contracts
• Access control policies
Strengths
• Ethereum interoperability
• Privacy
• Deployment and configuration
Weaknesses
• Small core development team and community
• Integration with external systems
• Management toolset
13. Parity
Key Capabilities
• Integration with both permissioned and public versions of Ethereum
• Support for side chains
• IPFS supports
• Messaging capabilities
• Privacy using secret stores
Strengths
• Ethereum interoperability
• Developer friendliness
• Tollset
Weaknesses
• Small core development team and community
• Integration with external systems
• Management toolset
14. Pantheon
Key Capabilities
• Integration with both permissioned and public versions of Ethereum
• Support for various consensus protocols
• Java-based extensibility
• Messaging and RPC interfaces
• Deployment via Docker containers
Strengths
• Ethereum interoperability
• Proof-Of-Authority consensus
• Whitelist-based access control
Weaknesses
• Small core development team and community
• Integration with external systems
• Management toolset
15. Corda
Key Capabilities
• Identity and access control via certificates
• Support for transaction workflows via the flow framework
• Integration with external systems via Oracles
• Application encapsulation via CorDApps
• Private node databases using Vaults
Strengths
• Privacy and access control
• Network topologies
• Workflow automation
Weaknesses
• Limited smart contract support
• Integration with external systems
• Small developer community
18. Azure Blockchain as a Service
Key Capabilities
• Support for different blockchains
• Integration with popular development frameworks
• Deployment and app lifecycle management
• Integration with Azure services
• Identity and access control
Strengths
• Tooling
• DApp lifecycle management
Weaknesses
• Limited smart contract support
• Integration with external systems
• Small developer community
19. AWS Blockchain as a Service
Key Capabilities
• Integration with AWS Services
• Identity and access control
• Integration with Quantum ledger
• Rapid provisioning
• Support for Hyperledger Fabric and Ethereum
Strengths
• AWS developer and partner communities
• Integration with external services
• Identity and access control
Weaknesses
• Small number of supported blockchain runtimes
• Limited tooling
• Basic integration with blockchain development tools and frameworks
20. IBM Blockchain Cloud
Key Capabilities
• Robust support for Hyperledger Fabric
• Integration with Bluemix services
• DevOps and automation processes
• Identity and access control
• Monitoring
Strengths
• Scalable Hyperledger Fabric topologies
• Privacy and security
• Fabric development workflow
Weaknesses
• No support for other blockchain runtimes
• Limited developer community
• Lack of support for open source blockchain development frameworks and tools
21. Kaleido
Key Capabilities
• Support for different variations of Ethereum blockchains
• Integration with open source enterprise systems and services
• Blockchain first capabilities like wallets or block explorers
• Integration with IPFS
• Native support for AWS
Strengths
• Native blockchain components
• Development tools and interfaces
• Rapid provisioning and deployment
Weaknesses
• Lack of support for non-Ethereum blockchains
• Small developer and partner communities
22. BlockApps
Key Capabilities
• Rapid Dapp development process
• Messaging interfaces via Kafka
• Compatibility with the EVM
• Monitoring tools
• Simple REST APIs
Strengths
• Simple Dapp lifecycle
• Docker support
• Toolset
Weaknesses
• Lack of support for non-EVM runtimes
• Limited developer and partner communities
• Very limited integration with external systems, security and other enterprise critical features
25. Integration
• Connecting to mainstream line of
business systems
• On-demand and scheduled execution
• Integration with data storage systems
• Bidirectional communication
31. Security and Privacy
• Ability to perform computations over encrypted data
• Hide specific aspects of blockchain transactions
• Use different privacy and encryption models in blockchain data
33. Data Storage
• Associate large datasets with blockchain
transactions
• Querying blockchain data on-demand
• Backup, restore and replicate large
datasets in a blockchain network
35. Summary
• The permissioned blockchain ecosystem is really crowded
• When establishing a blockchain strategies organizations should
consider the following steps:
• Select a blockchain platform
• Select a blockchain runtime
• Select complementary technology stacks
• Start small…iterate