- Use promo code PRIMEBOOKS18 to save $5.00 when you spend $20.00 or more on Books offered by Amazon.com. Enter code PRIMEBOOKS18 at checkout. Here's how (restrictions apply)
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.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Special offers and product promotions
From the Back Cover
It is not enough for Web application developers to be proficient injust one platform. As platforms grow and evolve, and as new onesarise, developers must be able to transfer their proficiency acrossplatforms in order to build complex Web applications effectively.This book helps developers understand the underlying coretechnologies so that they can learn new APIs and applicationframeworks more quickly.
Web Application Architecture provides an in-depthexamination of the basic concepts and general principles associatedwith Web application development, using examples that illustratespecific technologies. This conceptual knowledge is critical whenbuilding and deploying complex systems that are scaleable,extensible, maintainable and reusable. The book explains theunderlying protocols and languages that support Web applicationdevelopment, and delineates the best practices associated withbuilding robust applications. It describes mechanisms for providingWeb access to heterogeneous data sources including relationaldatabases and multimedia.
The new edition includes brand new and fully updated chapterson:
- Internet protocols - from TCP/IP to HTTP and beyond
- software components - servers, browsers, proxies andagents
- the dynamic web - how web applications present dynamicdata
- markup languages – HTML, XML and CSS
- tools, libraries and frameworks - AJAX, Struts, and Ruby onRails
- search technologies – underlying principles, applicationdesign, 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, programmersand system architects and designers alike. It provides acomprehensive, timely overview of modern web technology.
Visit the supplementary website atwww.wileyeurope.com/college/shklar
About the Author
Leon Shklar currently works for Thomson Reuters where he isthe head of technology for Reuters Media. Previously, Leon headedup the development team for the online edition of the WallStreet Journal at Dow Jones. Prior to joining Dow Jones, hespent six years at Bell Communications Research and almost as longin 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 IncomeSystems Group at Interactive Data Corporation. Previously, he wasan Application Architect at Dow Jones. Rich began his career atBell Labs, where his work with relational databases and theInternet prepared him the world of Web application development. Heis a co-author of Mac OS X for Unix Geeks, 4th Edition(O'Reilly). Rich holds an M.S. in Computer Science from StevensInstitute of Technology.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
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.
Most recent customer reviews
I highly recommend this book