You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
When is a database enough?
Identify the conflict that needs shared resolution before choosing a chain.
Three companies want to share reports. If they accept one operator managing a database, their main concerns may be access, backups and audit. If they want to verify claims independently, ask what they need to check: who signed a report, or which of two conflicting transfers of an entitlement should count? Those are different requirements.
Chapter 11 of 《区块链实战》 points out that a business may need only one of the technologies used in a blockchain. Following that insight means comparing specific designs rather than counting “yes” answers on a checklist.
| Requirement | Options to compare first | Conditions to establish |
|---|---|---|
| One organization maintains records for many readers | Database, access control and backups | Acceptance of that administrator |
| Parties check a report’s contents and signer | Signed files with shared storage | Key binding, versions and retention |
| Independent parties resolve conflicting updates | Shared ledgers, including blockchain designs | Validity, ordering, participation and governance rules |
This table does not select an architecture for you. Even a shared-state requirement should be compared against a database with audit controls, a trusted coordinator and other distributed systems.
What does “many participants” leave unanswered?
If one supplier controls every node and everyone else can only view a page, the node count alone has not reduced dependence on that supplier. Check who can validate independently, submit updates and change rules, and what happens when the operator leaves.
Someone must also operate the system over time. Without actual users, maintenance responsibility and a way to cover costs, demonstrating a transaction does not establish a reason to keep building.
Book and verification sources
This lesson develops a question from 《区块链实战》, Chapters 10 and 11, with the references below. It is a new explanation, not a book excerpt.
- NIST IR 8202 · Blockchain Technology Overview: mechanism and scope.
Check your understanding
Do three companies sharing reports necessarily need a blockchain?
No. Signed files and shared storage may be enough to check report contents and signers. Compare a chain only after identifying the actual requirements for shared updates, conflict resolution and administrative control.
Continue along a learning path
- From records to evidenceStep 5 of 5