Chainyard ref arch hyperledger global forum 2018 12-04 v0.97 ss

An asset library for practitioners in building Hyperledger-Fabric solutions
Mohan Venkataraman, Chief Technology Officer at Chainyard
Isaac Kunkel, SVP Consulting and Advisory
Reference Architectures,
Design Patterns and Governance
Credits: Aashish Shreshtha, Venu Vemula, Isaac Kunkel

WE TURN BLOCKCHAIN INTO BUSINESS RESULTS.
Copyright © 2018 CHAINYARD™️

TOPICS
Copyright © 2018 CHAINYARD™️3
REFERENCE
ARCHITECTURES
Blockchain Reference
Consortium Governance
Security & Deployment
Systems Architecture
Analysis Model
Data Design Patterns
Peer – Channel – Chaincode Patterns
Design and Code Patterns
Network Configuration Patterns
Business Patterns
DESIGN
PATTERNS

ABOUT CHAINYARD
❖ Deep expertise in Enterprise Blockchain Adoption &
Solution Implementation
❖ Focused on permissioned blockchains for enterprises
❖ Key contributor with IBM to Hyperledger Fabric platform
❖ Multiple projects on Hyperledger-Fabric & Ethereum
platforms
❖ Production ready solutions in multiple domains –
Financial Services, Asset Management, Procurement
❖ Expertise in Consortium Building and Governance
WE TURN BLOCKCHAIN INTO BUSINESS
RESULTS.
20+ Projects
4 in Production
2+ in Pilot Phase
3+ Projects > 18 Months
Morrisville, NC, USA Based

INTRODUCTION
EXPERIENCE AND RESEARCH DISTILLED INTO RE-USABLE ASSETS.
❖ This presentation is about “Reference Architectures, Design
Patterns and Governance”in building Hyperledger-Fabric
solutions
❖ The content of this presentation is based on our experience
since 2016 in 20+ Projects where each project is roughly
about 12 Weeks in duration
❖ We have consolidated the knowledge gained into a set of
reusable assets

CORE PRINCIPLES OF ARCHITECTURE
Leverage Hyperledger [Fabric] and exploit its
capabilities
Leverage the capabilities of channels, private
databases and encryption to provide data
and contract isolation
Utilize an appropriate identity and access
management system
Build security into the solution
Where appropriate, utilize tested and verified
open-source components
Design with potential for the network or any
component to fail
Comply with data protection and privacy
regulations, and other regulatory requirements
Design for scale, performance, extensibility
and reliability
Design smaller and focused contracts that can
be managed via criteria

7 Copyright © 2018 CHAINYARD™️
REFERENCE ARCHITECTURES

REFERENCE
ARCHITECTURES
BLOCKCHAIN
REFERENCE
CONSORTIUM
GOVERNANCE
SECURITY &
DEPLOYMENT
SYSTEMS
ARCHITECTURE
ANALYSIS
MODEL

BLOCKCHAIN REFERENCE MODEL
❖ Provides a logical path to decompose the
opportunity into various architectural elements.
❖ Enables consistent application of technology
and accelerates time to deliver.
❖ Promotes technology agnostic thinking about
the problem space.
❖ Supports interoperability through layering and
the creation of common components.
Interlinked set of components across the layers of
a Blockchain based solution.
B U S I N E S S
U S E R
B L O C K C H A I N
A P P L I C A T I O N
O T H E R S E R V I C E S
TOOLS
BLOCKCHAIN REFERENCE MODEL (BRIEF)

BLOCKCHAIN REFERENCE MODEL
REFERENCE

CONSORTIUM GOVERNANCE REFERENCE ARCH
❖ A consortium is a group of organizations with common
business interests and a stake in the blockchain.
❖ The reference provides guidance in establishing
governance.
❖ Start simple and small; then progressively elaborate
various business and technical aspects.
❖ Based on Chainyard experience in enabling its first
solution to go GA (General Availability) and consulting
on several others.
Establishes Checks & Balances for the
Blockchain to function effectively.
By-laws or articles of engagement
among consortium members
Network, Topology &
Operations
TECHNOLOGY CONSIDERATIONS
Governance
Process
Operations
Standards &
Guidelines
Auditing &
Control
Change
Management
Governance
Structure
Financial
Model
Incentive
Model
BUSINESS CONSIDERATIONS

Scans & Tests Connectivity
Infrastructure Platform
SECURITY & DEPLOYMENT REFERENCE MODEL
12
❖ This section identifies the key elements of the
blockchain that have to be tested for exposure to
external attacks and insider threats.
❖ The items identified are based on our assessment of
the internal solution prior to doing GA.
❖ Lack of comprehensive testing coupled with weak
legal agreements can lead to litigation, penalties
and fines.
❖ Security processes and legal agreements are within
the purview of Consortium Governance.
Key elements of the blockchain solution to be
tested for security risks and vulnerability.
User
Keys
Tokens
Database
Application
Smart
Contracts

SYSTEMS ARCHITECTURE REFERENCE MODEL
13
❖ Expose the Blockchain Application solution
functionality as API endpoints.
❖ Enable UI and Interfaces to interact via the Client
API Services. Do not bury application logic in UIs
and Interfaces.
❖ Enable trust - Attest all data to/from the
blockchain for non-repudiation between from
origin to destination.
❖ Use queues to prevent transaction loss when
handling large volumes.
The Blockchain is just one element of a broader
end-to-end solution.
PARTICIPATINGENTITIESAND
ORGANISATIONS
MESSAGINGSERVICES
CONNECTORS
UI/UX
CLIENTS(Node,Java,Python)
BLOCKCHAINNETWORKS
Entities Services UI/UX Clients Networks

MESSAGING
SERVICES
CONNECTORS
UI/UX
REST CLIENTS
(Node, Java,
Python)
BLOCKCHAIN
NETWORKS
Microservices
REST APIs
ORACLES
MQHub, ESB
Connectors
Node Application
Node SDK (Blockchain)
Client Specific
Local Database
Shared Cloud
Database
java
• Channels
• Endorsements Policies
• Ordering Service(s)
• Private ledgers
• Chaincode(s)
Colored Coins Cryptographic tokens Key Management
SYSTEMSSYSTEMS ARCHITECTURE REFERENCE MODEL
PARTICIPATING
ENTITIES AND
ENTERPRISE
APPLICATIONS

BLOCKCHAIN ANALYSIS REFERENCE
❖ Many blockchain initiatives ignore
important aspects – usually identified while
deep into the project.
❖ Any approach must focus on analyzing the
problem across the elements based on:
o Current Business Process Analysis, and
o Desired Target.
Focused Analysis of the Problem Domain is
critical to Solution Design.
Business
Model
Organizations Personas Assets Contracts
Audit &
Compliance
Integrations Policies
Application
Portal
Interface
Mobile
Interface
Environment
Information
Oracles
Transactions
& Business
Events

DESIGN PATTERNS

DESIGN
PATTERNS
NETWORK
CONFIGURATION
BUSINESS
DATA DESIGN
PEER-CHANNEL-
CHAINCODE
DESIGN &
CODE

HYPERLEDGER FABRIC – DATA DESIGN PATTERNS
❖ The Fabric provides various platform features.
❖ Data sharing between Organizations is
challenging because of personally identifiable
information, privacy, confidentiality, regulations
and transparency.
❖ Member organizations want to restrict sharing
of competitive and differentiating information.
❖ Data can be managed effectively using the
Fabrics features around public ledger, channels,
private database, transient data and encryption.
Data Patterns provide a guide on how and
where to store the data.
COLLECTION
OF DATA
CONFIDENTIAL
SELECTIVE
PUBLIC SHARE
PRIVATE
PUBLIC SHARE
PII

PEER - CHANNEL – CHAINCODE PATTERNS
❖ Organizations can run one or more Peers, aka
Nodes, on a blockchain network.
❖ Data and Process can be segmented between
two organizations by isolating them to separate
channels.
❖ Multiple instances of chaincode can be run on
same channel or different channels.
❖ Multiple chaincodes can be run on each channel
or across channels
Channels have an impact on how to design
scalable solutions.
cc1
cc2
….
ccn
cc1
cc2
….
ccn
SINGLE CHANNEL
MANY CHANNELS
SINGLE CHAINCODE MANY CHAINCODES
HIGH AVAILABILITY
NETWORK WITH MANAGEMENT PEERS
cc1
cc1
cc1
cc1
cc2
cc3

BLOCKCHAIN DESIGN AND CODING PATTERNS
❖ Working in Solidity and Ethereum has helped us
to understand how to design contracts as
stateless services.
❖ A set of reusable contracts can be composed
into solutions.
❖ Basic patterns utilized across many solutions
include Lookup, Registry, Data, Workflow
among others.
❖ Some patterns such as “Singleton”and
“Adapter”are also applicable.
Code Patterns will help accelerate trusted and
verified solution development.
REGISTRY ROUTER
WORKFLOWDATA & BUSINESS
DYNAMIC INSTANTIATION ACCESS VERIFIER

NETWORK CONFIGURATION PATTERNS
❖ Some Organizations are active network
participants and run nodes.
❖ As the network matures, Organizations may
prefer to bring in their private and public
business partners.
❖ Some partners may participate in the network as
users and not necessarily run nodes.
❖ The Business Network should be able to expand
with business and solution needs.
Networks start small, usually with only a few
organizations, and later have to be able to expand
and scale.
O
Orderer Pool
CA
A
Peer 1
B
Peer 1
Channel C1
CA
INITIAL NETWORK BETWEEN ORGANIZATION A & B

BLOCKCHAIN BUSINESS PATTERNS
22
❖ Business Patterns help in quickly
narrowing down opportunities within a
potential business domain.
❖ Patterns can enable better discussion
with the business and eliminate false
blockchain positives.
❖ Patterns can help identify internal
process or data quality issues versus
real blockchain opportunities
Most Blockchain opportunities fall into
certain business process patterns.
Identity &
Access
Management
Cross-border
Trade
Digital Asset
Registry
Audit And
Compliance
Financial
Settlement
System Of
Record
Data &
Document
Management
Secure Trade
Finance
Disputes &
Reconciliation
Provenance
Asset Track &
Trace

THANK YOU
Mohan Venkataraman, Chief Technology Officer at Chainyard
Email: mohan@chainyard.com
Office: 919-806-3535
Twitter: @vsmohan
Linkedin https://www.linkedin.com/in/movee97

Chainyard ref arch hyperledger global forum 2018 12-04 v0.97 ss

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Chainyard ref arch hyperledger global forum 2018 12-04 v0.97 ss

Similar to Chainyard ref arch hyperledger global forum 2018 12-04 v0.97 ss (20)

Recently uploaded

Recently uploaded (20)

Chainyard ref arch hyperledger global forum 2018 12-04 v0.97 ss