- What are the benefits of using a normal database instead of a blockchain? Auto confidentiality, no other entity views the content.
- What do you think the consequences would be of using a blockchain when you in reality don’t need one? Waste in cost of equipment and manpower
- Why should there be more than 1 writer to a database in order to justify a blockchain? One writer can not have consensus with itself
1 Like
-
What are the benefits of using a normal database instead of a blockchain?
SQL DBs are much cheaper to set up, update and maintain. They are much more efficient at reading and writing data. -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
The firm would incur significant costs for a solution that is much slower, more expensive and less functional than a traditional database. -
Why should there be more than 1 writer to a database in order to justify a blockchain?
If there is only one writer, this is likely a single trusted and accountable individual - there is therefore no need to achieve consensus/transparency between two untrusting parties.
Furthermore, BC wouldn’t even work in practice in such a scenario, as multiple nodes are required to achieve consensus, otherwise there is no decentralization/distributed ledger and one may just as well use a traditional DB.
1 Like
1.) What are the benefits of using a normal database instead of a blockchain?
A.) There are a few key benefits to decentralizing things instead of keeping it in a centralized server/database: Immutability; Security; Redundancy; Overhead/cost reduction;
2.) What do you think the consequences would be of using a blockchain when you in reality don’t need one?
A.) PERFORMANCE. iT IS SLOW COMPARED TO RDMS AND COST, IT IS MOR EXPENSIVE AND CUMBRSOME TODEVELOP AND MAINTAIN.
3.) Why should there be more than 1 writer to a database in order to justify a blockchain?
A.) TRANSPARENCY, TRUST AND SECURITY IF THERE IS MORE THAN 1 WRITER. TAMPERPROOF/ DATA IS TRUSTED.
1 Like
-
What are the benefits of using a normal database instead of a blockchain?
Normal databases are less expensive to develop and maintain, there is a more ready pool of talent to develop and manage them, and they costs less than blockchains to develop.
. -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
The major consequence is the loss of resources, including human and capital, on a project that ill suites the enterprise’s needs, -
Why should there be more than 1 writer to a database in order to justify a blockchain?
This allows for separation of functions, create redundancies and enhances the functionality of the database.
1 Like
- The benefits of using normal databases are that they’re faster, cheaper, and less time consuming to set up.
- Using a blockchain unnecessarily would be a waste of time, money, and human resources.
- A blockchain database is justified with more than one writer because you can eliminate the the need for trust and transparency with use of blockchain technology.
1 Like
- What are the benefits of using a normal database instead of a blockchain?
Faster and cheaper and easier installation
- What do you think the consequences would be of using a blockchain when you in reality don’t need one?
Expense, slower transactions and overly complicated
- Why should there be more than 1 writer to a database in order to justify a blockchain
Blockchain technology is immutable and secure…none of these things matter if there is only one person with database access
1 Like
-
What are the benefits of using a normal database instead of a blockchain?
It is faster and cheaper to run than a blockchain database. -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
It is costly and time-consuming or inefficient. -
Why should there be more than 1 writer to a database in order to justify a blockchain?
transparency and security.
1 Like
-
The benefits of using a normal database over a blockchain are cheaper maintenance, higher performance, and abundance of developers.
-
Higher costs, slower performance, developers are scarce.
-
Having more than 1 writer means that it is more difficult for 1 person to change data maliciously.
1 Like
-
What are the benefits of using a instead of a blockchain?
normal databases, , are relatively lower cost to implement and maintain and have higher speed of transactions -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
there may be no benefit gained, for the higher cost -
Why should there be more than 1 writer to a database in order to justify a blockchain?
if one (or more) party are trusted to Create/Write/ Read, Update and Delete (CRUD), what’s there to verify/Trust.
1 Like
-
A normal database is more efficient, easier to operate, and cheaper to operate when compared to a blockchain.
-
The consequences of using a blockchain when it is not really needed include higher costs and more difficulty to change data/transactions.
-
Transparency and added security.
1 Like
-
Quick. Efficient Storage. Less Costly. Already matured technologies.
-
Difficult implementation, difficult maintainace and huge costs.
-
If there is only 1 writer, security is not more a concern and that writers data will always be intact. For a blockchain, I believe atleast 3 writers should be there for proper consensus protocol.
1 Like
-
What are the benefits of using a normal database instead of a blockchain?
Using a SQL database or NoSQL database is easier to manage because it is clearer, people have more knowledge about SQL then blockchain, it is cheaper to create. It has some features that blockchains can not execute yet. But, blockchain allows other features that are very interesting, to develop. -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
Using a blockchain when it is not necessary will cost you money and probably time. -
Why should there be more than 1 writer to a database in order to justify a blockchain?
The goal of the blockchain is to have several nodes runnning and confirming UTXO’s, documentation, different stuff, if there is only 1 writter there is no point in having a blockchain.
1 Like
- cheaper to make, cost efficient.
- one of the consequences would be really expensive and slow.
- in terms of a private blockchain thats for security reasons so there is only one person who is making decisions they are directly involved in the business. not a bunch of different people who have nothing to do with that blockchain who would otherwise be on a public blockchain.
1 Like
[quote=“filip, post:1, topic:6389”]
-
What are the benefits of using a normal database instead of a blockchain?
Quicker, more resources and experience available, cheaper, private access is not shared -
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
expensive in time and financially, unnecessary complication for use and rules -
Why should there be more than 1 writer to a database in order to justify a blockchain?
in order to justify a BC, shared DB inputs are transparent, validated, immutable which eliminates untrusted middleman through consensus. When 1 writer only, no consensus is needed.
1 Like
1.The benefits really depend on the type of infrastructure your business needs. In general, you would use a normal database if you were to going to open up a traditional Finance business. Where certain levels of authority are given as well as the speed of transactions. If you wanted to build an anonymous distributing business then a Hybrid custom blockchain would be better suited. If you wanted to make a website, the complexity of a blockchain isnt needed.
2.It would make transactions longer (requests, or actual currency transactions) and it would also have more code that is unnecessary as well as more work load for your developers. Both Front and Back end.
3.To keep the “Trustless” component within the whole idea. You can better solidify and validate something with various writers. In a security standpoint, this makes it harder for any types of attack to blockchain network.
1 Like
What are the benefits of using a normal database instead of a blockchain?
Faster, cheaper, more resources available.
What do you think the consequences would be of using a blockchain when you in reality don’t need one?
The cost (in increased dollars, decreased productivity) will outweigh the benefit.
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 network & you don’t need a collaborative ledger to track transactions.
2 Likes
1. What are the benefits of using a normal database instead of a blockchain?
A: Faster implementation, less expensive, broader developer / user communities.
2. What do you think the consequences would be of using a blockchain when you in reality don’t need one?
A. Much greater expense and slower processing times.
3. Why should there be more than 1 writer to a database in order to justify a blockchain?
A: Blockchain would be used for multiple writers who have competing interests or who do not share mutual interest in the data. You would need the level of security that the blockchain can provide. This is not an issue with just one writer.
1 Like
1.cheaper, easier to find people with knowledge
2. more expensive, takes more time to find people with the right knowledge
3. to have more than 1 opinion on the subject of that 1 writer , increases transparency and security
2 Likes
More control over information and less transparency. This can be beneficial for businesses who want to keep their information private.
It can be hard to implement and most people in enterprise environments might not know much about blockchain technologies.
It provides more proof and is more distributed rather than centralized.
2 Likes
- An SQL DB is cheaper to implement and maintain. There are more people able to build and maintain a DB whereas the number of people who can build, scale and maintain a blockchain is limited.
- The firm will spend additional money which could have been used for investment in other projects. They could also lose focus on their end goals when trying to solve issues surrounding their blockchain.
- If only one writer to DB than that one should be trusted to maintain the DB which eliminates the need for a trestles blockchain. If that were to change to 2 writers who don’t trust each other than a blockchain may be needed.
2 Likes