You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sdk/storage-programs/README.md
+1-24Lines changed: 1 addition & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,29 +96,6 @@ Storage Programs are stored in the `GCR_Main` table's `data` column (JSONB):
96
96
97
97
Looking for implementation-ready patterns? Jump to the [Storage Program Cookbook](../cookbook/storage-programs/examples.md) for end-to-end recipes covering announcements, team workspaces, user profiles, and more. This overview keeps the focus on concepts so each scenario has a single canonical home.
98
98
99
-
## Comparison with Other Storage Solutions
100
-
101
-
### vs. Traditional Databases
102
-
- ✅ **Decentralized**: No single point of failure
103
-
- ✅ **Immutable history**: All changes recorded on blockchain
104
-
- ✅ **Built-in access control**: No separate auth system needed
105
-
- ❌ **Size limits**: 128KB per program (vs unlimited in traditional DBs)
Storage Program reads are served via RPC. They complete without a transaction, so there is no gas fee and responses typically arrive in under 100 ms. Writes still require consensus transactions; this guide focuses only on the read path.
0 commit comments