Marc-Thomas Schmidt, ESB Chief Architect
2006 is the year where ESB and SOA
"got real and our customers really switched onto" to these technologies, Schmidt
said during ESB-CON II.
From that uptick in ESB/SOA rollouts and adoption, Schmidt
seen "a very broad spectrum of integration problems can be tackled with ESBs
The broad needs of F1000 customers feeds directly into IBM's ESB Success Checklist.
lists the following must-haves for ESBs
Support a wide variety of entry patterns.
"Customers can choose from a wide variety of entry points," Schmidt
said, so the ESB solution you choose should let customers choose from them, including service brokering, web service gateways, app integration hubs and even an enterprise-wide SOA fabric
Provide strong 'time-to-value'.
should "be up and running quickly without requiring a lot of unnecessary hand-coding, or complex programming skills," Schmidt
Strong support for Reliability.
Many integration projects require high-levels of uptime, and customers should not be required to look to ESB add-ons to get that extra reliability.
had worked with a large bank to provide 99.97% reliability (for connections back to the central office) using an ESB solution.
Broad support for both heterogeneous environments and standards.
"Standards are important, but a lot of companies have non-standard technologies in place," Schmidt
said, "So and ESBs
need to support Open Standards as well as non-standard building blocks."