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
- Everything I know about good system designseangoedecke.com
- How to Build a Scalable Software Architecture for Business Growththemindstudios.com
- Do the simplest thing that could possibly workseangoedecke.com
- Production Twitter on One Machine? 100Gbps NICs and NVMe are fast - Tristan Humethume.ca
- In defense of simple architecturesdanluu.com
- The Architecture of Open Source Applications (Volume 2)Scalable Web Architecture and Distributed Systemsaosabook.org
- How to speed up development and hit the market faster - Indie Hackersindiehackers.com
- fast | catherine juecatherinejue.com
- How to design resilient and large scale data systemsblog.dataengineer.io
- The Alternative Implementation Problempointersgonewild.com
- Engineering Speed at Scale — Architectural Lessons from Sub-100-ms APIs - InfoQinfoq.com
- The Ultimate Database Scaling Cheatsheet: Strategies for Optimizing Performance and Scalabilitydzone.com