Most startups begin with a basic LAMP stack (on PHP or Python) and then add database replication and memcache as they grow. But then what? There's a big gap between these out-of-the-box solutions and what it takes to run something bigger.
Questions Answered:
What is LAMP?
When is LAMP a fantastic option?
At what point does it stop being a fantastic option? (maybe combine with above)
OMG the website is slow! What next?
What makes an application able to scale off a single machine/database well, while some cannot?
What off-the-shelf products have you tried to replace a traditional database?
When have you decided to roll your own data storage and query mechanisms? How well do those work, and how long do they take to build?
What have you tried that has turned out to be a bad idea?
What are some ways non-traditional databases can save money or headache before a site gets to the point where they are unreasonable?
If you had one piece of advice (with regard to future scalability) to give web application designers in the early stages of building their apps, what would it be?
Level:
Intermediate
Category:
Back-End Programming / Databases, Cloud Storage / Delivery, Information Architecture, New Technology / Next Generation, Web Apps / Widgets