comprised of four main components, and no one vendor currently
provides the best-of-breed technology for each of these components.
The four components--(a) transaction services, (b) data services, (c)
a services registry, and (d) orchestration technology--are defined below.
(a) Transaction Services -- These are services that most often come to
mind when one thinks of a Web service. Transaction services automate
business processes. For example, "create order" is a common
transaction service used to enter a new order into an order management
system. As the order progresses through the fulfillment process, it is
updated with other transaction services like "allocate inventory,"
"pick," "pack" and "ship." Essentially, transaction services create
and update data.
(b) Data Services -- These services read, display and analyze the data
that has been created -- typically with transaction services. Data
services help business users make long-term as well as day-to-day
business decisions. Data services help provide insight into an
organization, and they can reveal long-term trends such as correlation
between revenue growth and product quality, as well as
up-to-the-minute insight such as order status by customer.
(c) Services Registry -- This serves as a directory for all the
services available in an SOA. A registry contains the definition,
location, parameters and output for each service. It provides a simple
and standards-based means for publishing and discovering reusable
services. It is often the center for SOA governance, providing
visibility, reliability and control of all services.
(d) Orchestration Technology -- Also known as Business Process
Management (BPM), orchestration ties together services in a coherent
manner, and coordinates interactions among services. It manages the
interoperability of all services.
These four components work together to provide the agility that one
expects to derive from an SOA. Transaction and data services provide
the much talked about, loosely coupled services that expose a
company's systems as small, independent, yet interoperable pieces. How
and what each service does is listed in the services registry.
Developers look up the services that they need in the registry and tie
these services together using an orchestration tool to build a
business solution. Because components, particularly the transaction
and data services, are standards-based and interoperable, they enable
companies to quickly and easily build business solutions.
Although every component is necessary for a fully functional SOA, the
data services component is arguably the least talked about. Data
services and transactions are often lumped together without
distinction. Though each type of service behaves differently (as
briefly described above), the technologies used to create or enable
each type of service are dissimilar. In addition, industry analysts
predict that the ratio of Web services that are data services will
out-number transaction services by three to two. This highlights the
significance of data services as more companies deploy SOAs.>>
You can read this in full at:
http://www.line56.com/articles/default.asp?ArticleID=7637
Gervas
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
