SOFTWARE'S NEXT STEP

摘要

At the New York Board of Trade, prices of cotton, sugar, and other commodities can rise or fall a hundredth of a cent per pound—not much, until you consider that trades sometimes involve hundreds of thousands of pounds. In the few seconds it takes for a transaction to get executed, the price can change, and traders don't always know whether they made money or lost it. Until recently, it could take as long as two hours to get a preliminary confirmation that a trade was completed at a given price and even longer before the final outcome was verified. That lag largely disappeared a few weeks ago, when the Board of Trade switched from end-of-day batch processing to a new way of linking the systems involved in processing trades, cutting reporting times to 30 minutes. To do it, the Board of Trade created a services-oriented architecture that facilitates data sharing among the many systems involved in completing a transaction: its four trading systems, back-end accounting servers, clearinghouse system, and the computers of 39 trading partners. "A lot of pieces in each system were tied together," says David Sternberg, director of clearinghouse systems at the New York Board of Trade. Services-oriented architectures promise IT efficiency and flexibility in the form of reusable software "services." The concept, a few years in making, is hitting the mainstream now that commercial support for Web services is widespread. Yet the approach requires planning and know-how—services-oriented architectures are custom built, not bought. IT departments assemble them using a combination of development tools, XML-messaging middleware, other software standards, and management products. In the process, older applications may need to be reformatted for the services model.