Service-Oriented Architecture (SOA) allows businesses to create systems with the flexibility to reuse resources that are often found in silos across locations or departments. Realizing these benefits, however, requires both technological and cultural changes. Companies must re-examine the business and technology interactions that define requirements, as well as the processes used by developers in building systems and services.
With the volume of interdependencies that result from SOA frameworks, organizations that do not use a design-time governance solution bear unnecessary business and technological risk. Policies must be defined and enforced from day one. Relatively simple mistakes can proliferate over time and undermine the intended flexibility and agility benefits of the SOA process.
Point-to-point web
services, though relatively easy to create,
can quickly become unmanageable. The
benefits of designing a service and application
at the same time can be undermined when
business needs change, making these services
quickly outdated. And because web services
can be built quickly and easily, they
often proliferate without undergoing
proper definition of requirements. This
leads to various (and often poor) states
of quality.
SOA governance allows
for developers to govern policies at
various stages including: the outset
of development; when checking into a
source code repository; publishing into
a registry/repository; calling a service;
before it is executed by the server and
database; and throughout the full development
lifecycle until the service is consumed
by the end user.
WebLayers
automated governance for SOA helps to:
Ensure that every service is in compliance, while also gaining the necessary insight into all data and metadata needed to make informed decisions about business IT performance.
Make
your SOA deployment more adaptable to
changing technology, customer or industry
conditions. An application can check
with the system before it invokes a service,
thereby locating the most appropriate
service to satisfy its functional and
performance needs.
Allow
for full, automated governance to continue,
even as registry/repositories evolve,
and for organizations considering a transfer
to/from proprietary or open source systems.
