Unless they're part of a SOA suite that also includes an ESB, most SOA governance platforms cannot control services that have already been deployed. Their role at run-time is usually limited to the registry: Apps can query the registry, retrieving metadata they use to locate a service and any other services on which it is dependent. To enforce policies once a service has been invoked, governance needs to be integrated with run-time management.
Run-time Management
SOA management started off as Web services management and, as such, many of the same products can also be used in a JABOWS architecture. The theory is: An en-terprise with a large number of Web services can use management products to bring them under control, eventually building a SOA from the bottom up.
Because many users of Web services management don't have an ESB, SOA management systems duplicate many of the XML-processing and content-routing func-tions found in ESBs. However, they don't include service-enablement or orchestration: By definition, everything SOA management systems deal with is already a Web service, and there's little to orchestrate if services are not built into composite applications.
But a SOA management suite is more than just an ESB Lite. Its core function is run-time monitoring, checking that Web services meet SLAs or other performance metrics--features that ESBs lack. If performance is suffering, SOA management can help developers or IT managers by isolating faults and tracking dependencies among apps.
Bob Friday, Chief AI Officer for Juniper Networks, explains how the advanced technology is transforming operations.
Contact center leaders from 8x8, Awaken Intelligence, and 360insight discuss the importance of agent experience.
AI may force enterprises to rewire parts of their data centers so they are fully optimized to run such workloads. The question is do you use Ethernet or InfiniBand?
