Blockchain across Oracle

Understand the details and implications of the Blockchain for Oracle developers and customers

Robert van Mölken

• Publisher: Packt Publishing
• Year: 2018
• ISBN:
  9781788472166
• Edition: 1
• Topic: Computer Science
• Subtopic: Data Mining
• Index: Computer Science

Learn what the Blockchain is, what the differences between available blockchain platforms are, how to work with Oracle's Blockchain Cloud Service, and how Blockchain can change the direction of your Oracle work and the focus of your customers.

Key Features

• A professional orientation of the Blockchain for Oracle developers and customers
• Learn what the Blockchain is and how it will affect for you and your customers
• Learn how blockchain will disrupt traditional cross-organizational applications
• Implement your own Blockchain on Oracle and develop your first smart contract
• Industry directions of the Blockchain to help you decide where to develop your skills

Book Description

Blockchain across Oracle gives you the professional orientation to Blockchain that you need as an Oracle developer in today's changing world. Written and prepared for you by Oracle Developer Champion Robert van Mölken, this book gets you up to speed with the details of the Blockchain - core concepts, how to implement Oracle's Blockchain Cloud Service, industry implications for the Blockchain, and how the Blockchain will affect your Oracle customers.

Robert van Mölken introduces you to the history and concepts of the Blockchain. You'll really get to understand the Blockchain inside and out, as an Oracle developer or solution architect. You'll understand the Blockchain flow, and how the hashes and chains create a new decentralised paradigm for you as an Oracle developer. You'll gain insights into how the Blockchain affects Oracle developers and customers in this modern and disruptive era. You'll see how the Blockchain concepts work in this new world where Assets, Transactions, Security, and Privacy, can all be sustained across a decentralized system for your customers.

Then you'll find a detailed look at the cutting-edge Oracle middleware solutions. You'll learn about Hyperledger Fabric, the opensource Blockchain framework used by Oracle as its core, and how to set up your own Oracle Blockchain Network. You'll design and develop a smart contract, and learn how to run it on the Oracle Blockchain Cloud Service.

The final part of the book looks at how the Blockchain will affect your customers across various industry sectors. By studying industry trends in the financial services sector, healthcare industry, and the transport industry, you'll discover how the options and possibilities for you and your clients are being transformed by the Blockchain across Oracle. You'll complete this professional orientation by looking at Blockchain trends and future directions.

What you will learn

• A full introduction to the Blockchain
• How the Blockchain affects Oracle developers and customers
• Core concepts including blocks, hashes, and chains, assets, transactions, and consensus
• How to work with Oracle Cloud to implement a Blockchain Network
• Design, develop, and run smart contracts on the Oracle Blockchain Cloud Service
• Blockchain security and privacy for Oracle developers and clients
• Public and private Blockchain decisions for Oracle architects and developers
• Industry analysis across finance, governance, and healthcare sectors
• Industry trends and the future of the Blockchain technology

Who this book is for

This book is a professional orientation for all Oracle developers, solution architects, and decisions makers involved in Oracle system and future development.

Part I

Implications of the Blockchain

An Introduction to the Blockchain

This chapter serves as an introduction to the blockchain and its underlying technology. It requires minimal technical knowledge. It summarizes the content that you can expect to encounter in the upcoming chapters that go into greater depth. In this chapter, I will explain the blockchain technology is on a more architectural level, rather than describing every detail of each component or layer.

When you ask 10 people what they think the term blockchain means, you might not be surprised to get 10 different and conflicting answers, as use of the term blockchain can be a bit confusing. A lot of people connect it to Bitcoin (https://bitcoin.org/) or other virtual (crypto) currencies. Some people talk about the Ethereum Application Platform (https://ethereum.org), some about smart contracts (executable code), but most of the time, blockchain is explained as a distributed, shared ledger.

In essence, a blockchain is a system of maintaining digitally-distributed ledgers in a way that allows individuals who do not fully trust each other to agree on updates to the shared ledger. Blockchains use peer-to-peer protocols rather than a central authority or third party to distribute and verify transactions between entities. There is no single point of failure, so entities can appear, disappear, or malfunction without affecting the group.

In this chapter, you will learn about the following topics:

• What is a blockchain and how does it work?
• What is the architecture behind the blockchain ecosystem?
• What are the differences between public and private blockchains?
• How secure is a blockchain, and what about an individual's privacy?
• What kind of applications can run on a blockchain?

What is a blockchain?

When talking about blockchains, we always refer to it as a distributed ledger technology (DLT) that established the underlying, open source technology behind Bitcoin. A blockchain is a digital system of recording transactions of assets in a list that is replicated across available nodes in a network, rather than being stored in a central data store, as is the case with traditional databases.

In a distributed ledger such as a blockchain, the data is distributed to all nodes in a trustless manner (meaning without a trusted third party such as VISA, MasterCard, or your bank) using a peer-to-peer protocol in near real time. Each node individually processes and verifies every transaction redundantly, bundles the verified transactions into a block, and broadcasts them to all other nodes in the network. Through a consensus mechanism, the block of transactions is validated by other nodes in which the majority has to approve the block before it becomes final and is added to the blockchain. The blockchain uses a combination of digital signatures and cryptography to prove your identity and authenticity and to enforce read/write and execute permissions (access rights). This makes it possible to permit write access for certain participants and read access to other participants, or even to a wider audience; that is, everybody.

If you loosely compare a blockchain to a traditional database, a blockchain is a system that contains an ordinary database and some extra software that corroborates that submitted records conform to previously agreed-upon rules before adding the new records to the database. This extra software listens and broadcasts new records to all nodes, or peers, participating in the network, ensuring that each peer has the same data in its database. The following diagram is an overview of the capabilities that make up blockchain technology:

The major technologies used by the blockchain are divided into five groups, each representing a different layer in the architecture

Technically, a blockchain is a new method of data storage. It is actually just a file with a predefined data structure (that is, how the data is logically put together). It can be compared with other data structures, such as relational databases (tables, columns, and rows), XML files, comma-separated values (csv), Excel database files, and binary files (images and videos). An analogy that I often use is that blocks in a chain are the same as pages in a book. Each page in a book, just like this one, has a bunch of text structured in paragraphs, and information about its context (also called metadata), such as the chapter number, chapter title, and page number. Similarly, in a blockchain, each block consists of a collection of content, for example, the list of transactions, and a header, which contains technical information about the block, a reference to the previous block, and a digital signature (hash) of the data contained in the block.

A blockchain, where blocks are linked to each other to make a chain, is analogous to pages in a book. Pages use sequential numbering that makes it easy to know their order. If pages were to be pulled out of the book and thrown into a pile, it would be easy to put them back in order. A blockchain, though, is cleverer. The following diagram shows that each block links back to the previous block via the block's fingerprint. The fingerprint is determined by the individual block's content and the fingerprint of the previous block, as demonstrated in the following diagram:

Each block in the chain links back to its previous block, like page numbers in a book

In a book, the ordering of pages is implicitly built on a page whose number is one less; that is, page 13 follows page 12 (13-1), whereas blocks are represented by fingerprints or hashes that are built upon each other. For example, block 3 with hash 8ec6cc0 is determined by hashing its data together with hash 9a59c5f of the previous block. By using a fingerprint that is determined based on the previous one, it can be used for validating the internal consistency of the data.

This scenario is shown in the following screenshot:

Two blocks are linked together by their hashed fingerprints. The fingerprint of block #2 is based on its data and the fingerprint of block #1.

You can check whether the data is consistent within a block by generating the fingerprint yourself and comparing it to the one that is part of the block's header. If someone wants to change the information stored in one of the earlier blocks, they need to regenerate all of the fingerprints from that point until the end of the chain. However, the blockchain will appear to be altered, and it is instantly noticeable by others. Depending on the consensus method used, the creation of these fingerprints can be a very difficult and slow process, which makes it very problematic to rewrite the blockchain. Furthermore, the number of blocks already present in the blockchain can be huge, for example, for Bitcoin (June 3, 2018: 512253 blocks with a size of 156 GB). The following screenshot shows that when changing the data, the hash is also changed and the block becomes invalid:

The data in block #2 is changed, and it generates a different fingerprint than before

How does a blockchain work?

The technology (that is, the architecture, mechanisms, security, and so forth) behind the blockchain can be seen both as the backbone for future accounting and as an engine for a modern message transport system. So how does a blockchain actually work during runtime?

The following diagram shows how blockchain systems must follow a specific flow of actions in order to consistently maintain a distributed ledger of facts (a key-value database with the current state of assets) and a separate history of their updates (distributed transaction log). The transactions that you submit are stored and verified without the involvement of a governing central authority using advanced mathematics and computer science, that is, cryptographic hash functions.

The blockchain not only secures these transactions but also protects their integrity (and anonymity). This demonstrated in the following diagram:

The flow that a transaction follows from submission to being verified by the majority of networks

Now let's take a closer look at the preceding diagram that describes the flow of transactions in a blockchain. When you want to exchange data with someone else on the blockchain, you do this by submitting a transaction in which you propose your changes. A Transaction usually contains the context (action) in which it should be executed and any asset that can be described in digital form, such as currency, contracts, and incident and medical records. The Data structure of proposed changes to an asset can be both structured and unstructured, but often it is represented as JSON (JavaScript Object Notation), which is a human-readable text format for data objects.

A typical blockchain provides client APIs to interact with the transaction, but generally you would use a web application that calls the API with which you would submit your transaction to one of the active nodes (peers) in the network.

Depending on the network's capabilities, the transaction is either locally validated or directly broadcast to all active nodes in the network using the peer-to-peer network (P2P). When locally validated, your transaction is only broadcast after validation, based on a set of network rules. Each node that receives your transaction will, depending on network rules, either verify it instantly or transcribe it into a secure record and place it in a queue of pending transactions. In this case, nodes, in other words, the participating computers or servers in the network, verify whether your transaction is valid based on a set of rules to which the network has agreed.

For example, your transaction can trigger participating nodes to execute business logic (such as a smart contract) and follow the consensus protocol to verify the results. Some consensus protocols require you to pay a transaction fee to get your transaction verified. The amount you pay is part of your transaction, and it determines the time it takes to get verified. Some nodes that create blocks only verify transactions that have a higher reward.

Depending on the rules defined by the network's protocol, validating nodes combine transactions into a block and digitally fingerprint the result so that they can be validated by other nodes in the network. Just like transactions, blocks are broadcast to all active nodes using the peer-to-peer network. When consensus is reached, depending on the network' rules, participating nodes either batch the transactions and store the results as a cryptographically secured, immutable data block, or they take the approved block and append it to their ledger. Consensus protocols may include a reward system for nodes that create a block or require you to pay a transaction fee to distribute the currency to the rightful recipient.

Following the consensus mechanisms and network rules, it may take several blocks until you can be certain that your transaction is verified and not part of an orphaned chain. It is possible for multiple peers to ...

Table of contents

• Title Page
• Copyright and Credits
• Packt Upsell
• Contributors
• Preface
• Part I
• An Introduction to the Blockchain
• How Blockchain Will Disrupt Your Organization
• Part II
• Blockchain 101 - Assets, Transactions, and Hashes
• Blockchain 101 - Blocks, Chains, and Consensus
• Blockchain 101 - Security, Privacy, and Smart Contracts
• Understanding the Blockchain Data Flow
• Public Versus Permissioned Blockchains and their Providers
• Part III
• Ethereum Versus Hyperledger
• Building a Next-Generation Oracle B2B Platform
• Introducing the Oracle Blockchain Cloud Service
• Setting Up Your Permissioned Blockchain
• Designing and Developing Your First Smart Contract
• Deploying and Testing Your First Smart Contract
• Configuring, Extending, and Monitoring Your Network
• Part IV
• Blockchain Across the Financial Services Industry
• Blockchain Across the Transportation Industry
• Blockchain Across the Healthcare Industry
• Future Industry and Technology Directions
• Other Books You May Enjoy