# Week 4: Understanding Solana’s Account Model as a Web2 Developer
Solana's account model represents a shift from traditional Web2 development, where application state is stored in on-chain accounts rather than centralized databases. Programs on Solana contain logic but do not store state, which instead resides in accounts that hold data, tokens, and ownership information. This design enables parallel transaction processing and high throughput by predefining data access patterns.
- ▪On Solana, everything is stored in accounts, which hold data, tokens, program state, and ownership details.
- ▪Programs are stateless and can only modify accounts they own, similar to backend services executing logic.
- ▪Accounts must hold enough SOL to be rent-exempt, effectively prepaying for storage on the blockchain.
- ▪Transactions specify read/write accounts in advance, allowing Solana to execute many transactions in parallel.
- ▪User wallets sign transactions directly, replacing traditional API calls with on-chain authorization.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1170961) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Lymah Posted on May 16 # Week 4: Understanding Solana’s Account Model as a Web2 Developer #100daysofsolana #web2 #solana #blockchain #100DaysOfSolana (5 Part Series) 1 Your Solana Address Is Actually Your SSH Key: Understanding On-Chain Identity 2 Traditional Database vs Solana Accounts Comparison 3 From "Just Data" to "A Global Database": My Second Week Learning Solana 4 How Solana Transactions Are Different from REST API Calls (And Why It Matters) 5 # Week 4: Understanding…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
