Top

Guide to Web Application and Platform Architectures

March 19, 2010 by BPELworld.com 

Product Description

This book provides a general architecture and a taxonomy for web related standards and techniques, thus serving as a basis for professional development. Integration issues and the needed technologies are strongly emphasized and special attention is paid to metadata, process and organizational management. Main commercial approaches and products like Microsoft .Net, CORBA, EJB are also explained. The models and architectures discussed are illustrated with three accompanying real-world examples: order entry management, supply chain management, and mass customization.

Buy from Amazon –> Guide to Web Application and Platform Architectures

Share and Enjoy:
  • Digg
  • del.icio.us
  • Facebook
  • NewsVine
  • Reddit
  • StumbleUpon
  • Google Bookmarks
  • Yahoo! Buzz
  • Twitter
  • Technorati
  • Live
  • LinkedIn
  • MySpace
  • Share/Save/Bookmark

Comments

One Response to “Guide to Web Application and Platform Architectures”

  1. W Boudville on March 19th, 2010 1:11 am

    There are a whole host of web related technologies or methods or architectures out there. Choosing which of these to use to implement your web site application can be very difficult. The problem is that most texts are each about a particular choice of technologies. In contrast, this book offers a vendor neutral analysis of the main offerings. Which is the best virtue of the book.

    The authors explain the main methods for remote application development. Like Remote Method Interface [RMI] or Remote Procedure Calls [RPCs]. Heavily pushed by Sun Microsystems and others during the 90s. Also in that decade was the rise of CORBA and SOAP. These addressed the problem of code compatibility, when a program written in one language wished to call a routine in another program running on a different computer. Alas, CORBA’s binary nature and overall complexity was soon revealed.

    Then the book surveys the more recent Web Services. This has garnered its own slew of acronyms and standards – WSDL, UDDI, WS-BPEL etc. Just trying to keep a coherent picture of all this is very daunting.

    Plus, let us not forget Microsoft’s massive push into .NET, to compete with Sun’s J2EE. There is much common functionality between this. Though .NET binds you to Microsoft’s operating systems, and J2EE can be used outside Sun’s machines.

    Kudos to the authors for trying to help us through this mess.
    Rating: 4 / 5

Feel free to leave a comment...
and oh, if you want a pic to show with your comment, go get a gravatar!





Bottom