Scalability Tips: Greatest Hits
In the past two years we’ve written a ton of material on scalability. Here’s the greatest hits…
The internet stack is a complex infrastructure of interlocking components. An scalability engineer must be adept at Linux, plus webservers, caching servers, search servers, automation services, and relational databases on the backend. We think a generalist with a broad base of experience is most suited to the job of scalability engineer.
ORMs should keep you up at night, but so should coupled and locking processes, a single copy of your database, missing metrics and no deployment feature flags.
A followup to the original, we touch on Disk I/O, RAID, queuing in the database (a no-no), full-text searching, insufficient or missing caching and lastly the dreaded technical debt.
A Zen monk might ask what is the sound of one hand clapping? That’s the sound your servers will be making when you apply this one simple principal.
Deploying MySQL as your web-facing database? Here are a few key tips to boost speed & performance.
Building your startup in the Amazon Web Services cloud? There are 3 things you absolutely must do.
The cloud may seem like the obvious place to build new applications & infrastructure, but there is a precipice hidden from sight…
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)