Just-In-Time Architecture Scaling - Nathan Cahill
nathancahill.github.io · 317 words · saved by 1 readers
Any discussion about the architecture of a software project leads to arguments over the best way to achieve scalability. Essentially, it comes down …
Any discussion about the architecture of a software project leads to arguments over the best way to achieve scalability. Essentially, it comes down to finding a happy medium between the time required to develop a scalable architecture and how scalable that architecture will be. On one theoretical extreme, we could build a simple prototype of our software over the weekend, capable of supporting 100 users. Once we pass 100 users, we would have to restructure the architecture. On the other side, we could spend a year building rock solid software, capable of supporting 100 million users. This…
saved by
related reading
- Do Things that Don't Scalepaulgraham.com
- Do Things that Don't Scalepaulgraham.com
- Do Things that Don't Scalepaulgraham.com
- How to Build a Scalable Software Architecture for Business Growththemindstudios.com
- Do Things that Don't Scalepaulgraham.com
- Choose Boring Technologyboringtechnology.club
- ‘Give Away Your Legos’ and Other Commandments for Scaling Startupsreview.firstround.com
- Velocity is everything · Sid's Blogsidb.io
- #14: this definitely does not scalesubstack.com
- #14: this definitely does not scaleanotherbrowsertab.substack.com
- Big Ball of Mudlaputan.org
- Big Ball of Mudlaputan.org