-
What are the benefits of using a normal database instead of a blockchain?
Cost of creation and upkeep, employing understanding, speed… -
What do you think the consequences would be of using a blockchain when you, in reality don’t need one?
Extra cost, committed resources to a project that will not affect the bottom line, frustration -
Why should there be more than 1 writer to a database in order to justify a blockchain?
A blockchain stores interactions between users; if you lonely have one user, there is nothing to store.
1 Like
-
What are the benefits of using a normal database instead of a blockchain?
Databases are easier smaller scale and faster to develop than blockchains -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
You waist money and time -
Why should there be more than 1 writer to a database in order to justify a blockchain?
To not centralize the contents
1 Like
-
Q: What are the benefits of using a normal database instead of a blockchain?
A: Expense, conventional DB has a history, plenty of resources available to support -
Q: What do you think the consequences would be of using a blockchain when you in reality don’t need one?
A: Expense, blockchain is expensive, wasting money if not needed -
Q: Why should there be more than 1 writer to a database in order to justify a blockchain?
A: Trust (security), and a unified interest.
1 Like
-
A normal database be cost effective for the company, and a normal centralized database will faster, easier to manage with a central authority giving feedback directly to the company.
-
Expensive cost, shared data across a network of familiar individuals.
-
Because 1 writer (user) has all permission so therefore you would not need a Blockchain network.
1 Like
-
What are the benefits of using a normal database instead of a blockchain?
Fast.
works with trusted entities/accounts
central -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
It wouldn’t result in the right outcome because of the difference in key features in blockchain databases -
Why should there be more than 1 writer to a database in order to justify a blockchain?
if there is only 1 entity that writes. There is no need to use blockchain for checks and balances
1 Like
1- Since it is widely used, it is cheap to buy, set-up, find personnel to use it, can be modified easily, even changed or replaced by another database, and easy to understand the data in it.
2- Waste of time, resources and money.
3- When one writer , no problem if wrong doing or mistake, you know who did it.
With 2 writers now you need to introduce a system where trust is built into the system , changes are warranted (security and immutability), transparency to permissioned writers and viewers, and not to forget the history of Tx s .
1 Like
-
If we don’t need confidentiality or immutability, the normal database would be cheaper, more efficient, easier to query than the blockchain
-
More expensive, inefficient, more time consuming to utilize
-
having more than one writer in blockchain database ensures transparency, security and immutability
1 Like
What are the benefits of using a normal database
instead of a blockchain?
It’s more efficient, cheaper to use and easier to build.
Also the right competence is easier to find when building
a “regular” database
When it doesn’t require shared write access.
When you need or want a trusted 3rd party.
When you don’t need a database.
What do you think the consequences would be
of using a blockchain when you in reality don’t need one?
Expensive. Hard to build. Dificult to change functionalities. More slow.
Why should there be more than 1 writer to a database
in order to justify a blockchain?
The essentials of a blockchain is transparency and decentralization
and immutablility - the core in blockchain is also to trust
the transaction input of other entities. That removes the third party.
If only one writer there is no need for consensus.
1 Like
1. What are the benefits of using a normal database instead of a blockchain?
- much quicker to build
- much cheaper to build
- much easier to use
2. What do you think the consequences would be of using a blockchain when you in reality don’t need one?
Many, including:
- huge expense in terms of both time and money for a database that isn’t fit for purpose
- potentially causing problems with the existing IT infrastructure when trying to integrate the two systems
- potential loss of reputation of the project manager and/or the blockchain developer on the project if it all ends up a big over-priced mess
3. Why should there be more than 1 writer to justify a blockchain?
- In the case of only one writer, no one else needs to be trusted in terms of adding to or editing the database so no further safeguards would be required, therefore a normal database would be perfectly suitable.
1 Like
1. What are the benefits of using a normal database instead of a blockchain?
Normal database is efficient, fast, easier and cheaper to use than a blockchain database. If you don’t need the security, immutability, transparency and other benefits of a block chain, then use a normal database
2. What do you think the consequences would be of using a blockchain when you in reality don’t need one?
- Expensive
- Time intensive
3. Why should there be more than 1 writer to a database in order to justify a blockchain?
Because of transparency and security.
1 Like
- What are the benefits of using a normal database instead of a blockchain?
Normal database is easier to build ,maintain and more efficient thank blockchain - What do you think the consequences would be of using a blockchain when you in reality don’t need one?
Wasting resources and not efficient. - Why should there be more than 1 writer to a database in order to justify a blockchain?
Consensus model needs more than 1 user to share and come to agreement.
1 Like
- It is more effective in storing data
- It is expensive to develop, especially if you have to build from scratch. It will be difficult to integrate with existing databases
- to be able to justify actions/transactions within the network. With just 1 writer it would still be a centralized system.
1 Like
-
A normal database is less expensive, faster, more efficient in ways, and as the central entity you maintain full control over the data.
-
Creating a blockchain needlessly would cost a lot of extra money. It would take a much longer time to build, and would be less efficient for your needs.
-
There needs to be more than one writer to a blockchain so that txns are verified by multiple sources to prevent double spending.
1 Like
-
Using a normal database is cheaper and easier to change things.
-
If you used a blockchain and didnt need one you’d spend to much money and you’d piss off your trusted third party.
-
To use blockchain you need to have more than one node/writer to create the consensus required for blockchain to operate properly.
1 Like
-
What are the benefits of using a normal database instead of a blockchain?
Normal is cheaper and easier. -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
Expensive and time consuming. -
Why should there be more than 1 writer to a database in order to justify a blockchain?
To be able to trust a transaction.
1 Like
-
What are the benefits of using a normal database instead of a blockchain?
A normal database would be centralized, easier to create, and inexpensive. You would have total control as to its contents and management thereof. -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
The cost and the time it takes to create a blockchain specific to your company would be the biggest consequences in utilizing a blockchain when it is not needed. -
Why should there be more than 1 writer to a database in order to justify a blockchain?
Regardless of type of blockchain used, public, hybrid, or private, a consensus is required. By definition, a consensus is an agreement amongst more than one person.
1 Like
- What are the benefits of using a normal database insteSad of a blockchain?
Ease, cost, speed - basically everything, unless you need permissionless, transparent append & read only DB
- What do you think the consequences would be of using a blockchain when you in reality don’t need one?
Unnecessary cost, difficulty of setup and maintenance, speed issues
- Why should there be more than 1 writer to a database in order to justify a blockchain?
Most likely that one writer has full control anyway, he is basically the god of the system. So unless he has multiple identity disorder and trust issues with the “other guys in the house”, he would do just fine with a normal DB
1 Like
- What are the benefits of using a normal database instead of a blockchain?
A normal database is simpler and lower cost and allows for full control and privacy. - What do you think the consequences would be of using a blockchain when you in reality don’t need one?
Using a Bchain DB without need would make life and database management more complicated. - Why should there be more than 1 writer to a database in order to justify a blockchain?
If there is an outside party accessing a secure database then that entity needs to be trusted. A bchain solution allows for user access controls and adds that extra layer to protect the system from unauthorized breaches and potential damage [intentional or unintentional].
1 Like
- Databases are cheaper, easier and more efficient than blockchains.
- It could become quite costly and overly complex if your business does not need to use a blockchain and decides to do so.
- To avoid centralization of power.
1 Like
-
much cheaper, faster and private
-
Waste of resources and lot’s of expenses. wasting time.
-
If there is only one writer than there is no consensus
1 Like