Immutability - Not a Universal Law but a Trade-off part 2
The article discusses the implications of immutability in system architecture and data storage. It highlights how different types of databases handle immutability and the trade-offs involved. Ultimately, it emphasizes that immutability is not a universal principle but rather a strategic choice that affects scalability and system design.
- ▪Immutability affects persistence and system architecture across various database types.
- ▪Relational databases like PostgreSQL and MySQL are mutable by default, making immutability challenging.
- ▪Distributed systems benefit from immutability as it reduces coordination problems and simplifies data flow.
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 === 635971) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } ivan.gavlik Posted on May 18 Immutability - Not a Universal Law but a Trade-off part 2 #systemdesign #programming #software #architecture Immutability (2 Part Series) 1 Immutability - Not a Universal Law but a Trade-off 2 Immutability - Not a Universal Law but a Trade-off part 2 In the first part, we explored immutability through code, domain modeling, and APIs—starting from immutable functions, moving through state transitions, and ending with intent-driven APIs.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
