I started a proposal for Wiley publishing a long time ago on caching and networking for high performance web sites. Then I became employed by a company that forbade me from sharing (grrr) so I stopped.
I felt when writing the proposal though, that the solution isn't just client, just network, just server, or just anything... it's the combination of all parts and knowing how a change in one place impacts another part and how to balance them all to achieve the goal.
Even then, it's a stepped thing. A solution for a small but fast and resilient web site looks very different to a solution for a very large, distributed and fast web site.
A book should really include the basics building blocks in all major areas, and then offer suggestions on how to apply those building blocks at different levels of scale.
Indeed. I am trying to involve a former colleague of mine who is a specialist in front-end development and optimization to complete what knowledge i have on this front.
I have been actually thinking about asking HN or other about what they would like to see in this kind of book (keep in mind this is very PHP oriented as it's my specialty), instead of trying to come up with one myself and missing some important point.
I am also thinking into recycling presentation i was hosting at internal IT gathering, on very wide subject range (internal working of PHP and how to take advantage of that knowledge, Varnish usage, HTML5 video, How to profile a PHP application with XHProf and what to look for), and make video presentation out of them. Or may be just bundling this in the book, not really sure yet.
I started a proposal for Wiley publishing a long time ago on caching and networking for high performance web sites. Then I became employed by a company that forbade me from sharing (grrr) so I stopped.
I felt when writing the proposal though, that the solution isn't just client, just network, just server, or just anything... it's the combination of all parts and knowing how a change in one place impacts another part and how to balance them all to achieve the goal.
Even then, it's a stepped thing. A solution for a small but fast and resilient web site looks very different to a solution for a very large, distributed and fast web site.
A book should really include the basics building blocks in all major areas, and then offer suggestions on how to apply those building blocks at different levels of scale.