Blockchain is Complicated, can we just use APIs?

November 14, 2019
Evangelos Pappas

Evangelos Pappas

CEO of Ocyan

Hi, it’s Evan here from Ocyan, and on this short series of articles I’m trying to debunk some myths around the Blockchain technology, and approach the whole essence of the Practical Blockchain, and their use in the enterprise, across multiple industries.

If you are a sceptic against blockchain, or if you are considering to use Blockchain, or scale it in your organisation this might be a good source of information for you. On the other hand, If you are looking for an interesting ICO, crypto speculation or anything relevant, please skip this article 🙂.

Here we go,

Unless you have been living under a rock, the “Blockchain hype” has been a vibrant part of any business discussion. And as a usual response you must have heard a variation of one of the followings:

  • Don’t we have APIs already for that?
  • Why can’t I just use a database?
  • Too complicated to understand.
  • What if I want to edit past transactions?
  • Are launching an ICO?
  • Hasn’t bitcoin dropped to zero already?

And yes, there’s a little truth behind these smug statements, actually a lot of truth. Yet, being correct in your criticism, doesn’t make you accurate, let me explain.

Indeed, Blockchain came as a solution before we realise we have a problem. And it’s still in the soup of “Emerging technologies” that also include AR & VR, edge computing, quantum computing, autonomous things and so many other (there’s always a gartner article about it). But what is the problem?

1. Let’s just use APIs, forget blockchain

APIs are great, in fact I don’t think we have seen their full potentials yet, it’s the driven force behind the “as a Service” market and the hidden engine behind the next generation of Fintech transformation.

Cloud API Market

Cloud API Market

So job’s done then right? APIs are great, we will use them for everything and drop this Blockchain thingy to the garbage of the past, maybe somewhere along side with all the 90’s gadgets (I’m still missing my Sony Walkman).

1.1 API Economy

Ok, let me challenge you to pull out your Software Architect hat, and start a serious discussion. In a realistic scenario, your company needs to consume data from an API that’s managed by a startup, as your business grow you keep expanding these integrations and in a year of time you have ended up creating a network of partners that is reaching the number 50, and your B2B accounts team is telling you than another 100 are already in the sales pipeline.

Such an architecture case can be found in many industries such as adTech, fintech, insurances, logistics and many others.

Example Architecture

Example Blockchain Architecture

1.1.1 The struggle for the SLA

So far so good, your model is working fine, and your adoption is scaling fast, until that Saturday night, where you receive an alert that your response times are dropping below your promised SLAs. What happened? Your state of the art API can't go down, it has been tested so many times, you could vouch for it.

Well you run your forensics, and you see 10 of your partners have made an ad hoc deployment on Friday, and their API is timing out, making you look bad to your customers.

1.1.2 You can not rely on their SLA

It's tough, but after gathering your engineers, you realise that the best solution is to cache the data of your partners locally, so you can rely 100% on your infrastructure.

As a solution you pull out a database that you trust, and start storing the incoming requests with a timestamp, and amending versions to every response from the oldest to the latest. You have implemented a ledger.

Embeding DLT Tech

1.1.3 Everyone does it

This is great, 3 months later and your SLA hasn't dropped from the 99.998%. You make a white paper, you go to events to present it, until you realise it is a common practice, everyone does it. In matter of fact, some of your competitors have extend it to sync their ledger with their partners, no need for RESTful APIs, everyone uses grpc and certificates behind the authentication and authorisation.

1.2 You have reinvented Blockchain

You haven’t just reinvented the wheel here, but you managed to have crappy one indeed. You have created a DLT (Distributed Ledger Technology), a minimal version of what a blockchain is.

Quoting Gabriele Cacciola, CTO of Ocyan, in the question “whether a blockchain consortium makes any sense at all, and whether it can scale”:

1- In a consortium scenario, the API approach doesn’t scale. Imagine a consortium is made of 10 enterprises, this means that EVERY one of them will have to build 9 different API integrations and sort out the ETL of data internally. Moreover for every new joiner, you have to build a new integration 2- About it’s robustness. If I take your data as part of my dataset, I am building a system (and so a product) that relies on something that is completely outside my control and my premises. If the third party goes down, it causes a downtime to my product as well. This is unacceptable in most cases.

How could a blockchain standard approach solve this?

1.2.2 The Blockchain approach

A blockchain network is nothing more than a local datastore continuously syncing with the other nodes of the network about the data that exist in it. By having as a defacto layers of security, immutability and authentication blockchains allow you to create your integration logic right in the network without worrying if your partner is even online or miles and miles away, blockchains will make it like your data exist within your premises (which they are).

1.2.3 Blockchain Scalability

Blockchains are slow, true, but only when you want to store data on the network, performing reading operations and triggering models (aka smart-contracts, or chaincode etc) that’s fast! How fast? Well as fast as you can make your local nodes to run, for example in hyperledger/Fabric, one of the most adopted blockchains in the enterprise, the datastore usually is a standard couchDB.


Hello from Ocyan

Ocyan has been actively engaged with use cases from Tier-1 to Tier-4 organisations within the FinTech, Logistics, Energy, O&G and Telecom industries who have been trying to scale, deploy and manage blockchain applications within their enterprise environment. Our On-premise “Cloud Operating System” provides features such as the formation and management of trusted and secure blockchain consortia, back-office and legacy integrations with blockchain and P2P networks, and serverless data pipeline for any blockchain network. To stay tuned for more updates follow us on Тwitter or LinkedIn.

More further info about our features and use cases, feel free to Read More >>.



If you would like to stay tunned for the updates that we share, please  subscribe to our newsletter.  You may also follow us on  twitter  and linkedin.