| |||||||||||||||
Détails sur le produit
Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?
|
Much of the book is centered on how to load balance TCP (and to a lesser extent UDP), and the author uses HTTP and FTP as his primary driving examples. Throughout the book, the author provides some insight regarding what approaches real companies use (e.g. "this method is what Foundry and Cisco uses."), which I liked very much. Also, the illustrations were plentiful (although a bit primitive-looking).
There are only a few negatives about this book. The english writing is a bit stilted at times, and the chapters on firewalls and caches were basically rehashes of earlier chapters. Finally, I was hoping the author would have provided more detail on the load-distribution heuristics (which server to choose) with more metrics and actual real-world results.
I found the book to be extremely well organised. You will not get lost while reading this book, but you will need a university-level understanding of TCP/IP (and probably the link layer as well to get the NAT material) and networks in general to fully appreciate the matieral. Overall, a great book.
From a technical writing point-of-view, this is probably one of the best written books I have ever come across. The chapters are well organzied and are fairly easy to follow. Complex topics are clearly explained. The use of diagrams is very good as well.
If you want to learn more about load balancing, buy this book.
If you are interested in how load balancers are designed, this is the right book for you. However, if you are just shopping around and only want to know what load balancers are, get Brouke's one.
Btw, I was a bit disappointed at chapter 9. I expected to see more opinions on the future development of load balancers but it was not mentioned too much.
|
