This glossary supports the following titles:
SOA Design Patterns
Web Service Contract Design & Versioning for SOA
SOA Principles of Service Design
Service-Oriented Architecture: Concepts, Technology, and Design
Modern SOA Infrastructure: Technology, Design, and Governance
SOA with REST
Next Generation SOA: A Real-World Guide to Modern Service-Oriented Computing
SOA with .NET & Azure
SOA with Java
SOA Governance
SOA Security: Practices, Patterns, and Technologies for Securing Services
SOA and Cloud Computing: Practices, Patterns, Technologies
This glossary also supports the SOA Certified Professional (SOACP) program.
For more information, visit: www.soacp.com
and
www.soaschool.com
|
|
|
point-to-point
|
The term point-to-point originated from the EAI era during which many dedicated integration channels were established between different applications or environments. These integration channels allowed for the exchange of data between specific endpoints. In the world of service-orientation, a point-to-point exchange is comparable to a primitive service activity with a scope limited to a service and a service consumer program.
When viewed on its own, a point-to-point exchange is not considered a service composition. However, when the Service Abstraction design principle is applied, portions of a service composition may be hidden so that what appears to be a point-to-point exchange may in fact be a composition comprised of a controller and multiple composition members.
This term is primarily used to make a distinction between the message exchanges involved in primitive compositions versus complex compositions.
See also:
- service activity
- service composition
|
|
