Background and Goals

Software architects and developers choose XML parsing techniques, service libraries, encoding techniques, and protocols when building services using SOA techniques. Each choice has an impact on the scalability and performance of the finished service. In this example we have 3 goals:

1. Explain the changing landscape of APIs, libraries, encoding techniques, and protocols to software architects and developers. The current generation of technology choices changes approximately every 6 to 9 months. For instance, JAXB 1.0 is replaced by JAXB 2.0 and WebLogic Server 8.1 is replaced by WebLogic Server 9

2. Identify and use real-world, test use case scenarios showing software architects and developers how to choose technology based on their service goals

3. Deliver code compatible with the current techniques for building functional and scalability tests (black-box, unit, agile test-first). Many vendor tutorials are not compatible with what was used to build Appvance. While these packages could be modified with a lot of work, a better resolution was to develop kits with commercial, incorporating public information accessible to anyone

By pursuing these techniques we build a reusable method for evaluating Internet application performance and system scalability, plus the results feed basic business needs of cost/benefit and feature/function analysis including:

• Reduced hardware costs and reduced per-CPU licensed software by running more efficient services built with more efficient tools.

• Increased efficiency with lower network and processor bandwidth.

• Reduced time-solving interoperability problems with more effective tools.

The kit arms business managers and software developers with the evidence needed to recommend and adopt new solutions internally, and get their projects funded.