Service-Oriented Architecture Pays Off for Synovus Financial
The winning solution in the case study contest sponsored by the SOA Consortium and CIO magazine provided integrated business solutions using existing applications and legacy systems. Learn how they did it.
Do not underestimate the complexity of a distributed system, suggested Mize. "Start your SOA with a security standard for run-time security; do not let it evolve," he wrote. "Your SOA environment is only as good as your most poorly performing service." As a result, Mize recommends that companies adopting SOA put monitors in place to debug connection and data issues, such as real-time service statistics, network sniffers, and warehouse capabilities for service level agreement (SLA) management.
This was a huge project. In the process of creating its winning solution, the company learned—sometimes the hard way—how important governance is for reaching SOA project goals. They treated SOA as an architecture and philosophy, not a technology.
"You don't have to get all of the things right on the first implementation," wrote Mize. "But you do have to get your architecture correct."
