• 06/22/2007
    4:00 AM
  • Network Computing
  • News
  • Connect Directly
  • Rating: 
    0 votes
    Vote up!
    Vote down!

Analysis: SOA-Aware Network Infrastructure

When it comes to your service-oriented architecture, do you really need an ESB, management, governance and specialized security? And how do you choose a vendor partner wisely? Which components


IT BEWARE: Service-oriented architectures were supposed to be all about multivendor mashups and open standards, breaking applications up into services that can be easily stitched back together in new ways. But though SOA vendors still tout that path for applications, lately they're not practicing what they preach. It seems every one of them is buying up the competition or getting acquired, as they seek to build their offerings into suites that promise to fulfill all SOA needs at once.

It's an electrifying vision, but one that could force enterprises to buy more middleware to intermediate among different, competing middleware products. Moreover, despite pleas from users, Web services standards show no signs of stabilization.

Currently, the SOA intermediary software market is divided into four main product categories (see What Does What?" in the gallery). The most mature is the ESB (enterprise service bus), which shuttles data among services. In contrast, governance, a combination of catalog- and source-code management, is still in its adolescence. Both are always provided as software.

SOA-management systems and security gateways are equivalent to network-management frameworks and firewalls, respectively, and can be provided as hardware or software, sometimes even by the same vendor.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.

Log in or Register to post comments