Features
- Cover Type: Paperback with 440 pages
- Published by: Cambridge University Press February 13, 2000
- Written in: English
- ISBN 10 Number: 0521778492
- ISBN 13 Number: 978-0521778497
-
Book Dimensions:
9 x 7 x 1 inches
- Weighs: 1.6 pounds
Product Review
"Leander helps you understand the concepts behind the second tier so you can properly manage the processLeander does an outstanding job walking through the design, from actors to events, and in determining where the objects, methods and attributes liethe examples are excellentIf you're considering the n-tiered approach and feel a little fuzzy on the concept, or if you want a single practical book on the subject to supplement the more theoretical books and articles found in the technical journals, Building Application Servers is highly recommended." SD Times
Product Description
To address new demands in business computing,
software vendors are introducing application server toolkits. The concept is to create clusters of low-cost computers that support one specific business area, then connect these clusters to the corporate network. By using the network as the computer, one piece of
software can support desktop computing, electronic commerce, and communication with traditional mainframe software. Building Application Servers is a practical guide to application server technology, explaining the theory of network computing and providing practical techniques that use these tools to produce effective business solutions. Rick Leander includes practical examples and program code that use UML, Java, RMI, and JDBC to illustrate design problems and programming techniques. The development framework offered spans a variety of platforms, vendors, and middleware architectures.
software developers who are familiar with traditional client/server technology but want to learn how to move to distributed client/server computing will find this book invaluable.
Reader ReviewsAlthough application servers have been driving Internet Technology, there were virtually no books on them until now. The software architect will certainly find many things missing, but this book still manages to get at the heart of the matter and to get it well.
Search for books at
