Upgrade to Pro — share decks privately, control downloads, hide ads and more …

When not to use blockchain?

Koshik Raj
September 22, 2018

When not to use blockchain?

A talk on evaluating the suitability of blockchain for various use cases.
Agenda:
Understand the key properties of the blockchain technology.
Differentiate DLT from databases.
Understand decentralized application architecture.
Understand the blockchain suitability evaluation framework.

Koshik Raj

September 22, 2018
Tweet

More Decks by Koshik Raj

Other Decks in Technology

Transcript

  1. Agenda • Understand the key properties of the blockchain technology.

    • Differentiate DLT from databases. • Understand decentralized application architecture. • Understand the blockchain suitability evaluation framework.
  2. Bitcoin history • Several cypherpunks attempted to implement cryptocurrencies in

    1990s. ◦ Bit gold, DigiCash • "Bitcoin: A Peer-to-Peer Electronic Cash System" a paper was published by Satoshi Nakamoto. • It was implemented as a decentralized accounting system.
  3. Centralization concerns in the past • Cyber attacks on major

    institutions. ◦ Sony pictures, JP Morgan Chase data breach. ◦ Target customer confidential data breach. • Expensive transaction fee. • Subprime mortgage crisis in 2008.
  4. Distributed Ledger Technology (DLT) • A shared ledger that is

    distributed without borders. • Achieves a single truth in the decentralized network. • Blockchain + Peer to peer network + Consensus mechanism = DLT
  5. Consensus algorithm • A mechanism to reach an agreement in

    the decentralized network. • Achieves immutability and solves double spend problem. • Bitcoin uses Proof-of-work to achieve the consensus.
  6. DLT vs Distributed databases • Disintermidiation (DLT wins) • Confidentiality

    (DB wins) • Robustness (DLT wins) • Performance (DB wins)
  7. Questions to ask • Whether the scenario requires multiple entities?

    • Is the operation centralized? • Is the integrity of transaction history is required? • Is high performance required? • Is there any trusted third party? • Is there confidential data to store? • Does data need to be modified often?
  8. Blockchain decision model • Multiple entities. • The operation is

    not centralized. • Integrity of transaction history is required. • Performance is not the priority. • There is no trusted party involved. • Data transparency is desired. • Inserted data shouldn’t be modifiable (immutable)
  9. Thanks! Contact me: Koshik Raj linkedIn: koshikraj GitHub: koshikraj twitter:

    rajkoshik [email protected] www.koshik.me “keep calm and use blockchain wisely”