| copyright | lastupdated | ||
|---|---|---|---|
|
2018-10-30 |
{:new_window: target="_blank"} {:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:pre: .pre}
{: #disclainer}
Is this page helpful? Tell us.
ATTENTION: You must review the following information before you use any {{site.data.keyword.blockchainfull}} plans.
IBM's long history of leadership in innovation continues with the {{site.data.keyword.blockchainfull_notm}} offering plans on {{site.data.keyword.Bluemix_notm}}. {{site.data.keyword.blockchain}} is a rapidly progressing technology that is projected to disrupt the financial industry, local and global supply chains, and logistical support in any number of business spaces. Through various early adoption programs, IBM customers and business partners have been actively driving blockchain as an industrial solution. {{site.data.keyword.blockchainfull_notm}} on {{site.data.keyword.Bluemix_notm}} is one such program. As with any new technology, {{site.data.keyword.blockchainfull_notm}} on {{site.data.keyword.Bluemix_notm}} users should be aware of the potential for rapid and fundamental change.
{:shortdesc}
The architecture behind {{site.data.keyword.blockchainfull_notm}} is the Linux Foundation's Hyperledger Fabric project. Each open source community contribution improves Hyperledger Fabric but can present adoption challenges. IBM cautions against defining or exchanging financial assets directly on any Hyperledger Fabric blockchain network.
IBM recommends using Hyperledger Composer solely for demos and proof-of-concepts. IBM does not provide support for networks using Hyperledger Composer in production, including the Composer CLI, JavaScript APIs, REST server, and Web Playground.
{{site.data.keyword.blockchainfull_notm}} offering plans on {{site.data.keyword.Bluemix_notm}} are built on top of the Linux Foundation's Hyperledger Fabric stack. Hyperledger Project members, including IBM, continue to contribute to various subprojects under the Hyperledger umbrella. All contributions are reviewed, vetted, and tested by the community.
The following coding practices are NOT supported on {{site.data.keyword.blockchainfull_notm}} networks:
- Using associative arrays with iteration (the order is randomized in Go).
- Reading a list of items from a KVS table (the order is not guaranteed).
- Writing thread-unsafe chaincode (query and invoke might be called in parallel).
- Substituting global memory or cache storage for ledger state variables in chaincode.
- Accessing external services, such as databases, directly from chaincode.
- Using libraries or global variables that could introduce non-determinism (such as using "random" or "time").
In addition, it is not recommended to write non-deterministic chaincode, which introduces risk to data consistency and integrity. Note that the Hyperledger Fabric architecture is designed to counter against non-deterministic chaincode through a series of endorsement and validation checks. However, you are still strongly encouraged to code deterministic functions that are not reliant on non-static global variables, for example, time.