Systems Development Integration Business Processes: Interoperable Services
Systems Development Integration Business Processes: Interoperable Services
Systems Development Integration Business Processes: Interoperable Services
SOA separates functions into distinct units, or services, which developers make
accessible over a network in order that users can combine and reuse them in the
production of business applications.
These services communicate with each other by passing data from one service to another,
or by coordinating an activity between two or more services.
Overview
• Different groups of people both inside and outside an organization can use these
applications, and new applications built from a mix of services from the global
pool exhibit greater flexibility and uniformity
[Different groups of people both inside and outside an organization can use these
applications, and new applications built from a mix of services from the global pool
exhibit greater flexibility and uniformity. One should not, for example, have to provide
redundantly the same personal information to open an online checking, savings or IRA
account, and further, the interfaces one interacts with should have the same look and feel
and use the same level and type of input-data validation. Building all applications from
the same pool of services makes achieving this goal much easier and more deployable to
affiliated companies. For example: interacting with a rental-car company's reservation
system from an airline's reservation system.]
• A ''''Web service'''' (also Web Service) is defined by the W3C as "a software
system designed to support interoperable machine-to-machine interaction over a
network".
• Web services are frequently just Web APIs that can be accessed over a network,
such as the Internet, and executed on a remote system hosting the requested
services
• The W3C Web service definition contains many different systems, but in common
usage the term refers to clients and servers that communicate over the HTTP
protocol used on the Web. Such services tend to fall into one of two camps: Big
Web Services and RESTful Web Services.
• "Big Web Services" use XML messages that follow the SOAP standard and have
been popular with traditional enterprise. In such systems, there is often a machine-
readable description of the operations offered by the service written in the Web
Services Description Language (WSDL). The latter is not a requirement of a
SOAP endpoint, but it is a prerequisite for automated client-side code generation
in many Java and .NET SOAP frameworks (frameworks such as Spring, Apache
Axis2 and Apache CXF being notable exceptions). Some industry organizations,
such as the WS-I, mandate both SOAP and WSDL in their definition of a Web
service.
• More recently, RESTful Web services have been regaining popularity, particularly
with Internet companies. These also meet the W3C definition, and are often better
integrated with HTTP than SOAP-based services. They do not require XML
messages or WSDL service-API definitions.