It's never easy to run an airline. You have to worry about passenger loads on planes, and how these can best be allocated across routes. Then, there are services.
TechTarget's Rob Barry describes how JetBlue stress-tests its load infrastructure to make sure response times are up to par. As Rob describes it, "testers at JetBlue look at number of connections and compare it to response time. If response time for a Web service is anything exceeding one second, it could be problematic." JetBlue's team "will see how many concurrent connections the service can handle before performance starts to suffer. Average response time tends to be less than .5 seconds."
While many analysts and commentators fret about the lack of adoption of SOA, too much adoption poses an even more pressing challenge. As Rob observes, "when performing application load testing, it can be very difficult to predict the volume of traffic a new Web service will be subjected to. Even if initial predictions are accurate, a Web service often grows in use as external consumers outside of the enterprise connect into it."
Leave a comment