Building Scalable Web Sites

The book is rather old, but it is still great for those who want understand the topic from scratch. Recommended

This book, written by the lead developer of always-popular and it is quite possibly the best book (from a PHP/MySQL web app developer's perspective) ever written. If all of this knowledge comes direct from Cal Henderson's head then he's clearly a *very* clever guy.Covering everything from basic MVC concepts, bottle-neck analysis, code profiling and coding style through to network design, protocol choice and security, this book is really quite amazing in how much useful information it manages to pack into such a deceptively small book. I found myself highlighting large portions of entire pages and then realized that there wasn't much point because the whole thing deserved highlighting.If you're using PHP and MySQL (in particular) to build web-based applications that might one day serve more than a couple people - you should get this book and read it cover to cover.

The book is getting a little dated, but most of what's in here still makes sense. I actually put it away after reading 50% of it because it keeps making me feel stressed about all the things I haven't done yet with my own web application. There really is a lot of truth to the Getting Real approach of not worrying about scaling before you actually need to.I would have loved an abbreviated version of this book which might have told me the few things that are really worthwhile to start doing right from the beginning. Now I am mostly overwhelmed and may actually be more likely to ignore every concern listed in this book until just after it's too late.

For the negative reviewers of this book, I would ask one simple question: did you read on page xi of the Preface, the first sentence of the section that is titled “What This Book Is About”, which says: “This book is primarily about web application design…” This is not intended to be a book that goes into all the details of scaling all the different parts of a web application, for that would be a book primarily about implementation. It’s an overview of then current design considerations (2006), with general and particular discussions about web architecture, toolchains, data integrity and security, remote (or web) services, bottlenecks , the actual scaling challenges, system monitoring, and APIs. Yes, Henderson worked at Flickr at the time, but he moved on to Slack (so he’s a slacker, after all) and is the CTO and designer of their very successful application suite. It’s 2018, and we have open source frameworks, git and CI/CD, TDD, cloud hosting and horizontal scaling solutions aplenty, PAAS, SAAS, and hosted application monitoring suites, just to mention a few of the changes since 2006. And the dev tools are richer than ever. Nevertheless, this book is still relevant because it gives a coherent and cohesive account distilled from the lessons learned from designing, building, and maintaining a large, real-world website. It’s a useful book to read before one dives into more detailed books that provide up to date, modern implementation details.

The title should be "Overview Of Building Scalable Web Sites".I give it 2 stars not because it is a bad book but because I was tricked into thinking it was going to be useful as a scalable website builder. What you should do is look at the table of contents and research those topics and not bother reading this book.The book is more of an overview of the topics you need to consider when building scalable web sites. For example, if you are building a scalable website and the powers that be put someone who knows nothing about web sites in charge of managing you, this really is the perfect book to give to your new manager. Your new manager will get a clue, but your new manager won't know a thing about HOW to build anything, but will know ABOUT what is being built.The thing that got me is the first 188 pages of the book, just doesn't seem all that useful. On page 1 there is a definition of "What Is a Web Application", I'd estimate a book like this should assume you know what it is (it even suggests you do know what it is), but probably should save space and not even bother writing about it.Some sections and my summaries:Layered Software Architecture - could summarize into: DB layer, app code, html, css on topLayered Technologies - get appropriate book on actual topic such as DB book, and use a template languageGetting from A to B - separate program from markup, use a template systemHardware Platforms - dedicated, co-located, self hosting, space/power consumption, networkingIt took 26 pages to get through all of that. Indeed they are all very important topics (for the web builder and your new manager to know), but as a builder (if you've gone past the first "hello world" website) you should really know that you'll be using a database and writing web app code and using html and css. You should already know that in order to run a website, you'll need to run it on a computer which takes up space and power and needs to be networked. It's good to know that dedicated/colo hosting exists, but no need to write so much about it.It's almost like a book titled, "Building huge skyscrapers" and then goes on to say you are going to need construction equipment, concrete and steel. You'd hope the person interested in that book has already built houses or commercial buildings and has used construction equipment and concrete and steel already. I'm probably being too harsh here, but that's the jist of it.My "favorite" chapter is 3, "Development Environments". Use source control, have a good build system, track bugs. Those are very good rules, but to have 19 pages on source control AND 3 of those pages on RCS/CVS, it's like, "Are you kidding me? Isn't this book about building scalable websites?". Nowadays people probably have never even heard of RCS... (the book is a bit dated though).Chapter 9, Scaling Web Applications has some stuff about load balancing and database replication/master-slave info, but after reading the chapter, you still won't have the first clue of what load balancing system to use or how to setup database replication or clustering... but you'll know that load balancing and database replications exists and know a little about them.The actual best chapter is chapter 10, Statics, Monitoring and Alerting, there is information there that is useful. For your own sake though, look at the Nagios, Zabbix, etc monitoring packages and that'll get you started in the right direction.For the reviews which say this book is technical, I couldn't disagree more, if it was actually technical I wouldn't be so annoyed with this book. If it was technical, then you'd know HOW to do something after reading it...In conclusion, I think it's a good overview on the topics involved, but it's not really about building anything, it's about some topics you need to know that are involved with building a scalable website.

I liked the scope and thoroughness of this book, although I wish it had a little more information about writing web applications for the Windows/IIS/SQL Server/C# approach (WISC?), rather than Linux/Apache/MySQL/PHP (LAMP).Great chapter about internationalization, by the way. I've never seen a better description of UTF.

I had a technical recruiter suggest reading this book to help getting through technical FANG interviews. My feedback will be that they need to find an updated reading selection. A 13 year old tech book on web developments is just as outdated as you'd expect.

The book and the ideas discussed are a bit outdated (it was written in 2006). Especially on the hardware side. The advent of cloud services means the developer can abstract out a lot of hardware scalability concerns. Most important part of scalability is the database scaling. Only one chapter dedicated to it. Also, no discussion on how to design the application backend for scalability. The book is okay for basic practices of web site building.

Amazing book. It has all the details normal software engineer must know. All those questions are usually asked at job interviews and are useful in the normal live.

Beaucoup de banalités sur la gestion de contrôle et autres sujets bateau, l'auteur ne va pas droit au but. Les informations pertinentes tiennent dans une cinquantaine de pages, mais comme toujours chez O'Reilly, il faut faire du volume et donc broder sur des sujets en dehors de ce qui est annoncé.

Eines der besten Bücher, die ich seit langem zum Thema Skalierbarkeit und Web-Sites gelesen habe. Das Buch erklärt eigentlich alles, was man zum Thema "Wie baue ich einen webbasierten Service im Internet auf" wissen muß. Die Beispiele beziehen sich auf PHP und MySQL, sind aber auch übertragbar - auch Ruby on Rails-Programmierer werden von dem Buch etwas haben.Das Buch vermittelt keine kompletten Neuheiten, aber ich hatte beim Lesen viele interessante Aha-Effekte.Wer sich nur eine Website für fünf Besucher bauen will, für den ist das Buch uninteressant - aber sobald es in höhere Lastbereiche und damit andere Anforderungen und Skaliarbarkeit geht, da gibt das Buch viele Antworten.Der Autor ist übrigens Entwickler bei Flickr und bringt viele interessante Praxisbeispiele.

Wahnsinns Buch. Es beschreibt sehr viele Aspekte, die beim Erstellen von flexiblen, verteilten hoch skallierbaren Anwendungen zählen. Auch wenn nicht ganz zeitgemäß, so ist es als Einstiegslektüre bzw. zur Übersichtsgewinnung sehr geeignet.