Blockchain Decision Tree - Reading Assignment

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

    • A normal database will do a more efficient job in the sense that it is cheaper to operate, easier to operate and is quick compared to blockchain.
  2. What do you think the consequences would be of using a blockchain when you in reality don’t need one?

  • The consequences of using a blockchain when you do not really need one may vary. There are many consequences to come from using the wrong technology in business. With blockchain it is costly, requires a lot of effort, and is not as efficient in terms of doing the job a normal database could do in certain situations. Therefore using a blockchain when it is not needed comes with the consequences of wasted time and resources which is costly and may not even be functional in certain aspects of business.
  1. Why should there be more than 1 writer to a database in order to justify a blockchain?
  • More than 1 writer should be in a database in order to provide more transparency for all parties involved in the blockchain.
1 Like
  1. **What are the benefits of using a normal database instead of a blockchain?
    It’s cheaper, takes less time to implement, easier to find people who can manage it.
  2. **What do you think the consequences would be of using a blockchain when you in reality don’t need one?
    It would render processes to be slower and too expensive while the cheaper option of the traditional DB is available.
  3. **Why should there be more than 1 writer to a database in order to justify a blockchain?
    Otherwise transparancy wouldn’t really be an issue. Only 1 writer doesn’t guarantee security.
1 Like
  1. What are the benefits of using a normal database instead of a blockchain?
    Normal database implementation and administration is a well established area, there will be a lot of developers/consultant to hire or even you probably have the skills already in house and so is likely to be more cost effective.

  2. What do you think the consequences would be of using a blockchain when you in reality don’t need one?
    This may result in an end product that does not deliver the required functionality, is costly to maintain, does not gain user engagement and adoption. Implementing the technology for the wrong problem could mean, overlooking blockchain technology when it is the right solution due to bad past experience.

  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    If there is only 1 writer to a database, this is implying a trustless blockchain database is not required.

1 Like
  1. Cheaper, faster, and more efficient.
  2. Creating extra steps and delegation through a trustless system is pointless in a scenario where all parties are trusted.
  3. 1 writer is a single point of failure. Preferably 2 or more writers unknown to one another.
1 Like
  1. quicker, cheaper, more efficient

  2. It’ll just cost you a lot of money and a lot of time

  3. to cut out he unknown middle man

1 Like
  1. What are the benefits of using a normal database instead of a blockchain?
    It is fast to build, cheaper, and a party can have the control to access and modify any entries
  2. What do you think the consequences would be of using a blockchain when you in reality don’t need one?
    It would have a much higher cost of building it and operationally, it may lead to inefficient processes too
  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    Mainly because of transparency and trust, when using a blockchain, a consensus process it is in place which means that all parties have to agree in order to add new entries, trust is removed as well as a party that controls everything
1 Like
  1. There are several benefits of using a normal database instead of a blockchain, such as: Better at storing structured data, faster access, ability to update and delete, mature solution, lots of tech/options, easy to acquire skilled resources.
  2. Some of the consequences of using a blockchain when you don’t need one: First of all, it may be that you need a database for structure or performance reasons, or the ability to update and delete data. Also consider who requires write access, the level of trust among writers and whether you need a trusted 3rd party; these all have consequences.
  3. To justify a blockchain, there should be more than one writer, otherwise you might as well use a standard database. The benefits of blockchain are realized when there is more than 1 writer and you want to adopt a trustless model.
1 Like
  1. it’s faster, easier to load data, search data, and cheaper
    2.you won’t end up using it.
  2. because if it’s a single person, he does not need to verify or care about security
1 Like
  1. Normal databases are much cheaper, easier to design and more efficient to use.
  2. Using a blockchain when it wasn’t necessary would cost a lot of time, money and resources as well as making the whole system less efficient and slower.
  3. A blockchain is only justified when using multiple writers because the purpose of it is to take away the need for trust between users but with only one writer there is already no need for trust.
1 Like

1. What are the benefits of using a normal database instead of a blockchain? Fast, efficient, and cheaper because it doesn’t require the trustlessness of the network to verify transactions
2. What do you think the consequences would be of using a blockchain when you in reality don’t need one? Sensitive information and transactions will be seen by the public, added costs and complications
3. Why should there be more than 1 writer to a database in order to justify a blockchain? For consensus and verification

2 Likes

Decision Tree- Homework

1- normal DDBB are more efficient when it comes to access the data and cheaper too
2- loss of effciency and not cost effective
3- Because with only one writer we would have a centralized DB

1 Like
  1. CRUD databases are faster, more flexible, and can be managed by the company itself.
  2. Blockchains are designed to be immutable, and only get appended with new blocks, with a specific block format. So using a BC without needing one would mean that you could not update your data, or delete it, or change the structure.
  3. if there is only one writer, there is only one source of truth. RO operations can be done from a normal relational database easily. No need to over complicate the solution.
1 Like
  1. What are the benefits of using a normal database instead of a blockchain? It is easier to find the skills necessary to construct a traditional datbase, it is cheaper and more efficient to run.
  2. What do you think the consequences would be of using a blockchain when you in reality don’t need one? Inefficient use of resources, unnecessary costs, not achieving the functional requirements the user is looking for.
  3. Why should there be more than 1 writer to a database in order to justify a blockchain? One of the primary benefits of a blockchain is creating a trustless environment where user can be reasurred as to the data’s correctness due to a process of ensuring entries follow the rules. If only one person is writing information then they become the single source of truth and a trustless environment is both not possible, (you have to trust the author) and also unnecessary.
1 Like
  • What are the benefits of using a normal database instead of a blockchain?

It is cheaper, less complex, more programmers are available in the market.

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

Higher costs and complexity, harder to change functionality and rules, speed of use.

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

If only 1 writer, then you don’t have to worry about security. The point of a blockchain is that you don’t have to trust the users.

1 Like

1.Normal database are cheaper to implement and more tools are currently available to normal database
2.Using blockchain instead of database would make it unnecessary more expensive and slower
3. The main benefit of the blockchain is that it is trustless so if there is only one writer, there will be no need to trust another writer so the blockchain would be not needed in this case.

1 Like
  1. Cheaper to design, easier to write and read too, resource pool is larger
  2. Might not solve the needs of what you are trying to achieve as well as most likely costing more to develop
  3. If there is only one writer there is no need for consensus therefor no need for blockchain.
1 Like
  1. A normal database is far more performant.
  2. It would be a waste of resources.
  3. Because, it’s it’s just one writer, then a trustless solution is not reacquired.
1 Like
  1. Lower cost and high efficiency. Much easier to find people with experience with normal databases.

  2. Higher cost and slower. Hard to find people with experience in blockchain.

  3. Only 1 writer avoids concurrency issues and ensures trust and security.

1 Like
  1. What are the benefits of using a normal database instead of a blockchain?
    Most of the time you have lower costs and higher efficiency and it’s much easier to set up.
  2. What do you think the consequences would be of using a blockchain when you in reality don’t need one?
    It’s hard to find experienced people helping you and additionally there the possibility of having way higher costs which wouldn’t be necessary.
  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    It ensures trust and security doing it this way.
1 Like
  1. A normal database is cheap, efficient and has a lot of development history

  2. Using a blockchain when you don’t need one makes you less competitive (at least once the hype has settled)

  3. If there is just 1 writer (i.e. 1 user that requires database changes), he can generally trust himself (excluding the risk of hacks). Thus no blockchain is needed, which offers trust in a trustless environment.

1 Like