Blockchain Decision Tree - Reading Assignment

Blockchain Business Course
#501
  1. It is less expensive, more efficient, easier to manage and build normal databases.
  2. Building a more complex infrastructure than needed could result in wasted resources, like funding and time.
  3. Because of the complexity of the build, the need for censorship resistance, anti-corruption and transparency you would want more than one writer.
1 Like
#502

  1. Way cheaper, faster and able to surf anonymously.

  2. Too expensive, time consuming, hiring specialists (rare), and finally, lost of customers.

  3. At least ā€œ4ā€ members needed, consensus between members (security if trusted) and immutability.

1 Like
#503
  1. What are the benefits of using a normal database instead of a blockchain?
    speed efficiency and cost
  2. What do you think the consequences would be of using a blockchain when you in reality donā€™t need one?
    it requires a lot of maintenance and cost to upkeep
  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    trust and verification could be two important issues
1 Like
#504

  1. Normal databases are faster and dont require as much memory as BC and that makes it more efficient and changes are easier to make+ they are cheaper.

  2. Higher cost, more programming , time intensive.

  3. If only one writes then that is considered a trusted party and therfore the information is never checked by other than him, that is not the point of BC.

1 Like
#505
  1. What are the benefits of using a normal database instead of a blockchain?
    Itā€™s private, permissioned, easier to build and administrate, probably more efficient, cheaper,ā€¦
  2. What do you think the consequences would be of using a blockchain when you in reality donā€™t need one?
    The project would probably fail, expenses would be enormous high; depends on data tx, maybe slow, maybe even you canā€™t design/structure it the it would be needed
  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    It would make no sense, since there is no one else to verify.
1 Like
#506
  1. faster and cheaper.
  2. expensive, slow.
  3. no need to share.
1 Like
#507
  1. What are the benefits of using a normal database instead of a blockchain?
  • Normal DBĀ“s are faster, easier and cheaper to build ā€“ particularly as there is not need for a speciality skill set.
  1. What do you think the consequences would be of using a blockchain when you in reality donā€™t need one?
  • It is important to focus on what the criteria and user needs are, using a Blockchain could be a waste of time and money if it were not necessary.
  1. Why should there be more than 1 writer to a database in order to justify a blockchain?
  • If there was just going to be one writer, it would be an unnecessary waste to use a Blockchain as there would be no need for trust, transparency or immutability.
1 Like
#508
  1. Normal database is cheaper, easier and more efficient.
  2. Waste of money, time and resources.
  3. Because of transparency and immutability.
1 Like
#509
  1. A normal database allows for edits and insertions easily
  2. It would make work and records difficult and stiffer (harder to change or adapt).
  3. More than one writer makes sense for a blockchain because it is really about verifying communication
#510

  1. What are the benefits of using a normal database instead of a blockchain?
    A normal database is less expensive to setup and maintain and has many people available who are qualified to work on it. To implement a normal database would involve relatively simple project management and change management.

  2. What do you think the consequences would be of using a blockchain when you in reality donā€™t need one?
    Your decision making process could be brought into question. Your expenses could be unnecessarily high. Your staffing requirements could be hard to fulfill.

  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    If there is one writer (of state), then a blockchain does not provide any additional guarantees than a regular database. On the contrary, a database would be more suitable as it is more efficient in terms of performance. from: https://hackernoon.com/to-blockchain-or-not-to-blockchain-45004a23e8a7

1 Like
#511

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

  • cheaper, quicker to implement,

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

  • Business would not see a return on investment, and may be even more costly to revert back to a traditional system.

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

  • because with more than one writer, the system demands trust. The whole point of blockchain is to eliminate as much trust as possible between parties.
1 Like
#512

  1. What are the benefits of using a normal database instead of a blockchain?
    Low cost, easy to setup and maintain

  2. What do you think the consequences would be of using a blockchain when you in reality donā€™t need one?
    Youā€™d be wasting money on infrastructure and setup of a system you donā€™t need.

  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    Because blockchain only makes sense when there is a network (meaning more than one) to ensure the security of the network.

1 Like
#513

1: they are far more efficient at reading everyday data. Most common with people so there are more use cases for databases such a SQL.

2: Extremely slow and inefficient work environment. Transactions would not be the primary focus as that would be why it would be effective.

3: Because a blockchain is decentralized so there should usually be more than one programmer working on the source code itself, plus it takes a very long time.

1 Like
#514
  1. Normal database are mostly centralized, making it easier to govern and implement specific protocols.
  2. Blockchains are transparent all transactions will be visible. Most companies would not want their business transactions available for everyone to see. Blockchain data cannot be modified, for companies that require that flexibility of data manipulation.
  3. For security, authenticity - more nodes equals decentralization and less single point of failures.
1 Like
#515
  1. A normal database is less expensive and does not have to go through the tedious process of integration.
  2. If you integrate a Blockchain when not needing it you will lose a lot of money and find yourself in a position, where you could lose partners that are not on board with the idea. I think that unless you are in Insurance or Supply Chain you should outline exactly how Blockchain would work and if your partners are on board with the idea.
  3. One key element of the Blockchain is that it is transparent and helps with efficiency among multiple parties. If you have one writer in your database then you will have no validators or need for consensus and would be wasting money when your normal database could work just fine.
1 Like
#516
  1. What are the benefits of using a normal database instead of a blockchain?

Normal databases allow for centralization, confidentiality and privacy. A single entity can have full control over a set of data without concerns for immutability and transparency.

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

Waste of resources (money to build the network, timeā€¦) and overall a loss in efficiency and gains.

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

One of the blockchainā€™s applications is to able to share data among entities in an efficient way - Having a single writer is therefore not a relevant use case for blockchain technology.

1 Like
#517

  1. What are the benefits of using a normal database instead of a blockchain?
    Normal Databases are cheaper and more efficient to implement. In addition there is way more experience in implementing normal databases and therefore more resources having normal database knowledge.

  2. What do you think the consequences would be of using a blockchain when you in reality donā€™t need one?
    It would be a waste of time and money and would likely result in a failed project and unhappy customers.

  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    Because you wouldnā€™t need a blockchain if there is only 1 writer because then you donā€™t need a trust less environment. A minimum of 2 writers having different interests would maybe justify the use of a blockchain.

1 Like
#518
  1. a normal database is cheaper and efficient as there are more skilled workers to build this solution.
  2. The consequence os using a blockchain when it is not needed is that it would be expensive, provide slow user experience, and potentially not fullfil all queries.
  3. There should be more than one writer to ensure transparency and security.
1 Like
#519

  1. What are the benefits of using a normal database instead of a blockchain?
    Centralized, low cost, implementation and maintenance is inexpensive with a wide variety of individuals with the skill set to readily perform these activities.

  2. What do you think the consequences would be of using a blockchain when you in reality donā€™t need one?
    Overcomplication of your technology model, more expensive, requires higher level of skill to implement and maintain.

  3. Why should there be more than 1 writer to a database in order to justify a blockchain?
    One does not need a blockchain for oneself. One needs a blockchain to facilitate immutability and higher security protocols a standard database cannot deliver.

1 Like
#520

1. What are the benefits of using a normal database instead of a blockchain?
A: A ā€œregularā€ technology database, say a SQL Database is more efficient to query, easier to implement, cheaper to deploy and maintain. This means that, unless one is going to take advantage of its immutability, transparency and decentralized features, it may not be the best option

2. What do you think the consequences would be of using a blockchain when you in reality donā€™t need one?
A: Higher implementation and running costs, lower performance and reduced flexibility.

3. Why should there be more than 1 writer to a database in order to justify a blockchain?
A: Because this situation does not require a trustless approach.

1 Like