Salesforce Architecture - How they Handle 1.3 Billion Transactions a Day
highscalability.com/blog/2013/9/23/salesforce-architecture-how-they-handle-13-billion-transacti.html
From the page
Saved with the link. Notes from 2007 to 2016 are mostly the page's own words, so this is probably an excerpt.
The following is an architectural overview of salesforce.coms core platform and applications. Other systems such as Heroku's Dyno architecture or the subsystems of other products such as work.com and do.com are specifically not covered by this material, although database.com is. The idea is to share with the technology community some insight about how salesforce.com does what it does. Any mistakes or omissions are mine.
Same host · 17 links from highscalability.com
- Pinterest Architecture Update
- High Scalability - Scaling Pinterest - From 0 to 10s of Billions of Page Views a Month in Two Years
- NYTimes Architecture: No Head, No Master, No Single Point of Failure
- 10 Things You Should Know About Running MongoDB at Scale
- 10 Tips for Optimizing NGINX and PHP-fpm for High Traffic Sites