Blockchain Decision Tree - Reading Assignment

Blockchain Business Course
#221

  1. a normal db is cheaper and easy to implement. You should opt for a normal db when you don’t necessarily need one with the characteristics of a blockchain (immutable, trustless,…).

  2. you will have much more costs for planning, implementing (and maintaining?) the blockchain and maybe for training the employees who will work with it.

  3. a blockchain makes sense in a scenario where there is more than 1 person involved. With only 1 writer you won’t need a solution whose strength is the possibility to involve parties that don’t need to trust each other

1 Like
#222
  1. normal databases are fast, easier efficent and cheaper. if you don´t nedd security, immurtability, transperency of a blockschain, then use a normal db
  2. That could be a waste of resources, time and money.
  3. Because of transparency and security.
1 Like
#223

  • What are the benefits of using a normal database instead of a blockchain?
    A: Faster and cheaper.

  • What do you think the consequences would be of using a blockchain when you in reality don’t need one?
    A: Inefficiencies and lack of speed and higher cost are the price you would pay when using a blockchain unnecessarily.

  • Why should there be more than 1 writer to a database in order to justify a blockchain?
    A: With only one user the interests are aligned by default so there is no need for a trustless system.

1 Like
#224
  1. What are the benefits of using a normal database instead of a blockchain?
    A normal database is easier and cheaper to build and maintain, and it is easier to find people who can build it, understand it and interact with it. It’s easier to upgrade, and, if you have an existing database that is maybe SQL, then it would be more efficient to upgrade than to add an unnecessary blockchain.
  2. What do you think the consequences would be of using a blockchain when you in reality don’t need one?
    Using a blockchain when you don’t need one would not be cost effective. It is costly to build a blockchain because it is time consuming and also there are not so many people who understand it. If you add to an existing IT system when you don’t need to, you could end up with an over complicated network that needs expensive staff to run and maintain it, or even something that is not running well and makes the IT infrastructure unworkable.
  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    With only one writer there is no need for consensus.
1 Like
#225

  1. A normal database is easier, cheaper and more efficient.

  2. It will cost more and consume more time setting up the database.

  3. If there’s only one writer there’s no need of a blockchain, it would be pointless.

1 Like
#226
  1. What are the benefits of using a normal database instead of a blockchain?

Normal Database is faster for transactions, cheaper to run, requires less memory so is more efficient,

  1. What do you think the consequences would be of using a blockchain when you in reality don’t need one?

It could be very ineffective and costly to maintain.

  1. Why should there be more than 1 writer to a database in order to justify a blockchain?

There should exist more than one writer because that is the definition of a Blockchain where multiple writers sent transactions.

2 Likes
#227

  1. Normal DB is faster, cheaper, more efficient, more resource availability, and when the typical features of a BC are not needed such as immutability, decentralized, permissionless, trustless, etc

  2. Slower, more expensive, less control, scaleability issues, etc

  3. So that not one entity holds the monopoly on control. The purpose of the BC is for full consensus and permissionless state

2 Likes
#228
  1. What are the benefits of using a normal database instead of a blockchain?
  • You have total control of who can and cannot be a user/participant
  • Information and data stays confidential within your organisation
  • You can choose which third parties entities to audit or authenticate your services
  • Cheaper and uses less resources ie. More efficient
  1. What do you think the consequences would be of using a blockchain when you in reality don’t need one?
  • Waste of money and resources
  • Poor user experience as blockchains can be slow and inefficient
  • Less flexibility for development and upgrades
  1. Why should there be more than 1 writer to a database in order to justify a blockchain?

If there is only 1 writer, then your system is centralised and controlled so no need for a blockchain. Only with 2+ writers is there decentralisation and therefore better security and transparency.

1 Like
#229
  1. faster, no need if only one party views/edits information, it is usually much cheaper to create, run and maintain; also easier to find people that know how to build/run one
  2. unnecessary costs involved, delays or obstructions in workflow
  3. if there is no second writer to approve at the least decisions made by the first, everything can be basically done in an excel spreadsheet and would have the same effect as the only one to trust is yourself, even if you are dishonest; if there are more parties involved, traceability, verification and validation is mandated
1 Like
#230
  • What are the benefits of using a normal database instead of a blockchain?
    1.It is inexpensive to run as there are many talent that can implement it across a Centralised IT Infrastructure.
    2…
  • What do you think the consequences would be of using a blockchain when you in reality don’t need one?
    1.You may not be able to conform to future adaptation and introduce new product and experience for clients.
    2.Other start ups in your same line of business may find a usecase to be able to appeal to broader client beyond your closed network because of diversity
    3.It maybe a redundant tech that cost you extra if you do not use it efficiently for it’s purpose if you decide to implement it.
  • Why should there be more than 1 writer to a database in order to justify a blockchain?
    1.Because the essence of blockchain is to verify rather than trust,if you are not in a business that involves multi parties which is difficult,then you do not need the new tech.
1 Like
#231
  1. Mainly it’s a cheaper, faster and simpler set up
  2. Maybe it’s sounds good for a company to say buzz words for PR. But really it comes down to lower profitability since the investment will cost more than benifits.
  3. Because otherwise there would be zero need for a blockchain database, since one writer cant share data only with it self.
1 Like
#232

Perhaps this…

3 Likes
#233
  1. A SQL DB have a much shorter access time, easier to query, (you may update entries as you wish).
  2. A waste of computational power, time loss, anxiety.
  3. If there is just one writer, this writer can control the entire DB and thus corrupt it as much as wanted anyway. No consensus required.
1 Like
#234

Now this looks really interesting! thanks for sharing it! I hope other students can find it useful :slight_smile:

Carlos Z.

1 Like
#235

1 Cheaper, more efficient, faster and much easier to find skilled resources

2 Increase the project cost and development time

3 No need for a distributed DB with consensus among multiple writers

2 Likes
#236

  1. A normal database has faster access, scalability and performance. Also is easier to implement.

  2. It would increase the cost and the comprexity, functions, speed, protocols, etc.

  3. A blockchain wouldbe in order if the writers don’t trust each other, don’t have the same interests o don’t have a third trusted party between them.

1 Like
#237
  1. The benefits of using a normal database instead of a blockchain are:
  • read/write/delete-controlled;
  • cheap;
  • fast and efficient;
  • 3rd party access;
  • select user administration.

  1. Using a blockchain where it is not necessary can be expensive to implement and support, slow transaction processing.

  2. A blockchain should have more than 1 writer to maintain immutability of the network via a consensus.

1 Like
#238
  1. What are the benefits of using a normal database instead of a blockchain?
    Faster, cheaper, more optimized, can easily be implemented with the existing IT infrastructure.
  2. What do you think the consequences would be of using a blockchain when you in reality don’t need one?
    Money and time spent on a project that will not bring a lot of value. Implementation will take a lot as there is not much expertize in the domain and the systems might malfunction.
  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    If there is only one writer there is no need to have a blockchain. A SQL database is more suited for such cases.
    The more writers there are, the more transparency and security there is on the blockchain.
1 Like
#239
  1. It’s easier and cheaper to build a normal database.
  2. Expensive, hard to find skilled devs as it’s emerging tech.
    3.Because that 1 writer decides everything, he is the manager, a trusted source. If however you want more people to have this role, then you need transparency and you should use a blockchain.
1 Like
#240

  1. A normal database is faster, more efficient, cheaper and there are more developers available with traditional DB skills.

  2. More expansive, slower and scalability issues. It might be harder to integrate it into the system landscape of the business.

  3. If there is only 1 writer the advantages of BC DB can not really be utilized (e.g. immutability, decentralized, permissionless, trustless)

1 Like