- Deployment Bottleneck with QSOA
- Retaining QSOA for Amadeus Access /Load Balance
- Dependency on XML transforms in QSOA: small requirement change generates bulk code change
- slow development of new service
- No change in apps code ,only url change
- Use new REST based service along with older SOAP WSDL service
- Fast development of new service
- use Node.js async mode to give access to more customers in peak time.
- Nodejs : more traffic through put in same time
- Qrest able to take both wsdl and REST http: no code change in apps , only url change for new transforms
- Qrest able to capture old QSOA response: as above
- Only router portion of QSOA [service bus] used : no QSOA deployment after the first router
- XML transforms replaced by java : agile friendly,compact code
- Load balance and router role of QSOA remain unchanged
Made with Slides.com