- Paperback: 440 pages
- Publisher: Wiley; 2 edition (April 27, 2009)
- Language: English
- ISBN-10: 047051860X
- ISBN-13: 978-0470518601
- Product Dimensions: 7.5 x 0.9 x 9.2 inches
- Shipping Weight: 2.2 pounds (View shipping rates and policies)
- Average Customer Review: 11 customer reviews
- Amazon Best Sellers Rank: #242,748 in Books (See Top 100 in Books)
To get the free app, enter your mobile phone number.
Web Application Architecture: Principles, Protocols and Practices 2nd Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
From the Back Cover
It is not enough for Web application developers to be proficient in just one platform. As platforms grow and evolve, and as new ones arise, developers must be able to transfer their proficiency across platforms in order to build complex Web applications effectively. This book helps developers understand the underlying core technologies so that they can learn new APIs and application frameworks more quickly.
Web Application Architecture provides an in-depth examination of the basic concepts and general principles associated with Web application development, using examples that illustrate specific technologies. This conceptual knowledge is critical when building and deploying complex systems that are scaleable, extensible, maintainable and reusable. The book explains the underlying protocols and languages that support Web application development, and delineates the best practices associated with building robust applications. It describes mechanisms for providing Web access to heterogeneous data sources including relational databases and multimedia.
The new edition includes brand new and fully updated chapters on:
- Internet protocols - from TCP/IP to HTTP and beyond
- software components - servers, browsers, proxies and agents
- the dynamic web - how web applications present dynamic data
- markup languages – HTML, XML and CSS
- tools, libraries and frameworks - AJAX, Struts, and Ruby on Rails
- search technologies – underlying principles, application design, and SEO
- future directions and emerging technologies – XML Query, RDF, and the Semantic Web
Ideally suited for course usage and self-study, this practical, engaging textbook is essential reading for students, programmers and system architects and designers alike. It provides a comprehensive, timely overview of modern web technology.
Visit the supplementary website at www.wileyeurope.com/college/shklar
About the Author
Leon Shklar currently works for Thomson Reuters where he is the head of technology for Reuters Media. Previously, Leon headed up the development team for the online edition of the Wall Street Journal at Dow Jones. Prior to joining Dow Jones, he spent six years at Bell Communications Research and almost as long in the world of dot-coms and Internet software. Leon holds a Ph.D. in Computer Science from Rutgers University.
Rich Rosen is a senior developer in the Fixed Income Systems Group at Interactive Data Corporation. Previously, he was an Application Architect at Dow Jones. Rich began his career at Bell Labs, where his work with relational databases and the Internet prepared him the world of Web application development. He is a co-author of Mac OS X for Unix Geeks, 4th Edition (O'Reilly). Rich holds an M.S. in Computer Science from Stevens Institute of Technology.
Top customer reviews
The authors do not try to provide authoritative reference material for all the sundry topics, instead giving enough salient details to explain the reasons why we have the array of tools available today. They hold to a very determined balance of subject depth versus brevity, successfully maintaining the thread of their narrative throughout.
All the usual players are here: LAMP, DHTML, Ajax, XML (et. al.), PHP, SEO. While familiar with most of the material to some degree, I found the book filled in gaps in my understanding and illuminated connections that I had not considered before. The authors' approach of historically-informed, progressive development-- something akin to first principles-- provides a solid foundation for evaluating design choices and for continued learning after the book is finished.
Near the end, we are brought so up to date that clear choices no longer present themselves. Struts is presented next to Ruby on Rails and Java Server Faces and HTML5 are briefly discussed. Such are the vagaries of an active and developing field. This book can show us how we got to today, but at some point, the current edition will no longer carry you to the forefront, nor leave you confident and comfortable with current production systems. Still, it's value will hold for the foundation it provides and the approach to thinking about further developments.
What I especially liked was the historical perspectives which explained how at one time a particular approach was considered a best practice, but that current best practices have changed, (accompanied with explanations on why the change occured.)
What I especially liked were that diagrams (in somewhat conventional and consistent standards) were used throughout, which has an added benefit of suggesting a standard for Architects to follow on their projects (I am shocked how many architects and development leads are completely clueless on how to draw UML or SOA-modeling diagrams; and it seems like every person has to use their own unique approaches, usually not related to anything published by thought leaders in analysis and design techniques.)
I also liked that there are recommendations on what architectures work best in certain situations; many books ramble on and on about an approach and either (a) at the end conclude that it is not the best approach (so why waste my time for several pages!?), or (b) worse, offer No conclusions, advice, or best practice recomendations.
Again - I am not completely finished with this book, so there may be some weaknesses and strengths I have missed in this review.
Also - I always, strongly recommend NOT relying on One Single Book as a reference (personally I usually have 3 to 5 books on the same topic so I get a balanced viewpoint), so I will never rate this book as "the best" or "a comprehensive" reference.