Although blockchain technology is still perceived in the corporate environment as something far removed from the realities of enterprises, the world is not standing still. And blockchain is increasingly being used to solve various tasks, and there are many challenges in implementing this technology.
They say that it is impossible to make it faster, better and cheaper, but you will not go far in the implementation of blockchain in the enterprise if will be satisfied with only two of these qualities.
So what are the main obstacles to implementing blockchain technology. When choosing an appropriate solution, you need to answer at least the following questions.
– Does the “solution” meet the standards of the industry’s reference architecture? Without this, it will not be able to integrate into industry systems for public and private blockchain transaction processing. It’s unfortunate, but you can’t do without profit-hungry middlemen just yet. All of the infrastructure, processes and systems that make the world go round (and do a pretty good job of it), if they are to be scrapped and replaced by something coherent, it won’t happen tomorrow.
– Does the “solution” fit into the reference architecture of the OSI model? Since blockchain is sometimes referred to as Web 3.0, the Internet of Value, or any other sales and marketing jargon, the solution should fit the most current industry standard that most closely resembles the OSI articulated standards for networks, the Internet, and web services. Yes, technology, like standards, must evolve to meet new usage scenarios for mass consumption.
– How is it easier to fit your blockchain “solution” into the Enterprise Technology Framework? This enterprise technology framework defines the technology services and functions (IT capabilities) required to support business applications and data. These include common (or shared) application services, common system and data services, network services, security services, platform services and administration tools that enable IT service delivery. It may also be helpful to identify the specifics of the business or new business service that may be required. Or, in the case of a hybrid cloud model, which system or service should be based in the enterprise data center (e.g., System of Record) and which can be offered in a public cloud SaaS model or made available through a System of Engagement via a smartphone or other mobile device. Enterprise Technology Framework environments provide a blueprint for solving business problems including applications, services, systems and data. And blockchain can relate to some of the above.
In addition, when thinking about finding a problem that your blockchain “solution” should solve, you need to think about the architectural principles underlying it. Failure to think holistically about this issue is fraught with challenges (in technology and business, individual and enterprise level) that blockchain will not be able to solve. Note that these are not architectural “givens,” they are architectural drivers or principles that require some sort of overcoming to truly embrace and utilize.