Skip to content

Commit 6563527

Browse files
author
tcsenpai
committed
removed comparisons
1 parent 952d272 commit 6563527

2 files changed

Lines changed: 3 additions & 33 deletions

File tree

sdk/storage-programs/README.md

Lines changed: 1 addition & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -96,29 +96,6 @@ Storage Programs are stored in the `GCR_Main` table's `data` column (JSONB):
9696

9797
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.
9898

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)
106-
-**Write costs**: Transactions require consensus (vs instant writes)
107-
108-
### vs. IPFS
109-
-**Mutable**: Update data without changing addresses
110-
-**Access control**: Built-in permission system
111-
-**Structured queries**: Read specific keys without downloading everything
112-
-**Size limits**: 128KB (vs unlimited in IPFS)
113-
-**Not free**: Writes require transactions (IPFS storage is pay-once)
114-
115-
### vs. Smart Contract Storage
116-
-**Flexible structure**: No need to predefine schemas
117-
-**JSON-native**: Store complex nested objects easily
118-
-**Lower costs**: Optimized for data storage
119-
-**Simple API**: No Solidity/contract coding needed
120-
-**No logic**: Cannot execute code (pure storage)
121-
12299
## Core Concepts
123100

124101
### Address Derivation
@@ -229,4 +206,4 @@ Ready to build with Storage Programs? Head to the [Getting Started](./getting-st
229206
- [Access Control](./access-control.md) – configure permissions safely
230207
- [RPC Queries](./rpc-queries.md) – build fast read paths
231208
- [Cookbook Recipes](../cookbook/storage-programs/examples.md) – apply patterns in real apps
232-
- [API Reference](./api-reference.md) – look up method signatures
209+
- [API Reference](./api-reference.md) – look up method signatures

sdk/storage-programs/rpc-queries.md

Lines changed: 2 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,7 @@ Learn how to efficiently read data from Storage Programs using RPC queries.
66

77
## Overview
88

9-
Reading Storage Program data is **free** and **fast** because it uses RPC queries instead of blockchain transactions:
10-
11-
| Feature | RPC Query | Blockchain Transaction |
12-
|---------|-----------|------------------------|
13-
| Cost | **Free** | Requires gas fee |
14-
| Speed | <100ms | ~2-5 seconds (consensus) |
15-
| Rate Limit | RPC provider dependent | Block production rate |
16-
| Use Case | Data reading | Data writing |
9+
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.
1710

1811
## Basic RPC Queries
1912

@@ -669,4 +662,4 @@ async function timedRead(addr: string, key?: string) {
669662

670663
- [Examples](../cookbook/storage-programs/examples.md) - Real-world query patterns and use cases
671664
- [API Reference](./api-reference.md) - Complete API documentation
672-
- [Operations Guide](./operations.md) - Learn about write operations
665+
- [Operations Guide](./operations.md) - Learn about write operations

0 commit comments

Comments
 (0)