Transport/protocol abstraction
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Transport/protocol abstraction" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Transport/protocol abstraction|concern=Fails [[WP:GNG]]}} ~~~~ Timestamp: 20250329062652 06:26, 29 March 2025 (UTC) Administrators: delete |
This article relies largely or entirely on a single source. (March 2024) |
Transport abstraction is the ability to change service transport protocol implementations in a configuration file with no change to business logic implementation code.
Transport abstraction may be achieved through the use of standardized connectivity interfaces within for all service transport protocol implementations.
This architectural abstraction offers great benefit to architects and developers, as it lowers risk involved with regard to technologies and service protocols deployed. An organization may determine at a later date that a different protocol is required. This may then be changed at run time via a configuration file.
The originally deployed service transport protocol might also be augmented with another service implementation in a differing protocol, configured to offer the same business logic implementations or a subset thereof.
This architectural abstraction also allows alternative environments (e.g. development, testing, etc.) to simplify deployment configuration without change to the business logic implementation code.
References
External links