Service Messaging

CategoryWeb Services Standards

Application layer messaging protocols and API descriptions formalize client-server interfaces that use common data interchange formats. By following standard conventions, development teams can increase productivity, take advantage of tooling, and focus on the business matters.

Standards Overview

Standard Web API Specifications

Continued lack of trust and parallel development of disparate system solutions leads to an ever-increasing web of organization and domain-specific application interfaces. Standardization of a lightweight protocol for exchanging information in a decentralized, distributed environment comes to the rescue: well-defined application interactions replace duplicate ad-hoc code per service provider or consumer.

The following publications standardize application layer messaging for web-based resources:

  • ISO/IEC 19464 — Advanced Message Queuing Protocol (AMQP) 1.0
  • ISO/IEC 20922 — Message Queuing Telemetry Transport (MQTT) 3.1.1
  • RFC 7540 — Hypertext Transfer Protocol Version 2 (HTTP/2)
  • RFC 7230 — Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
  • RFC 7231 — Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
  • RFC 7232 — Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
  • RFC 7233 — Hypertext Transfer Protocol (HTTP/1.1): Range Requests
  • RFC 7234 — Hypertext Transfer Protocol (HTTP/1.1): Caching
  • RFC 8187 — Indicating Character Encoding and Language for HTTP Header Field Parameters
  • RFC 2817 — Upgrading to Transport Layer Security (TLS) within HTTP/1.1
  • RFC 8446 — Transport Layer Security (TLS) Protocol 1.3
  • RFC 6585 — Additional HTTP Status Codes
  • TMF640 — Open API: Activation and Configuration
  • TMF651 — Open API: Agreement Management
  • TMF642 — Open API: Alarm Management
  • TMF646 — Open API: Appointment
  • TMF655 — Open API: Change Management
  • TMF681 — Open API: Communication
  • TMF678 — Open API: Customer Bill Management
  • TMF629 — Open API: Customer Management
  • TMF667 — Open API: Document Management
  • TMF662 — Open API: Entity Catalog Management
  • TMF691 — Open API: Federated Identity
  • TMF673 — Open API: Geographic Address Management
  • TMF675 — Open API: Geographic Location Management
  • TMF674 — Open API: Geographic Site Management
  • TMF658 — Open API: Loyalty Management
  • TMF668 — Open API: Partnership Type Management
  • TMF683 — Open API: Party Interaction Management
  • TMF632 — Open API: Party Management
  • TMF669 — Open API: Party Role Management
  • TMF676 — Open API: Payment Management
  • TMF670 — Open API: Payment Methods
  • TMF628 — Open API: Performance Management
  • TMF649 — Open API: Performance Management Threshold
  • TMF654 — Open API: Prepay Balance Management
  • TMF644 — Open API: Privacy Management
  • TMF620 — Open API: Product Catalog Management
  • TMF637 — Open API: Product Inventory Management
  • TMF679 — Open API: Product Offering Qualification
  • TMF622 — Open API: Product Ordering
  • TMF671 — Open API: Promotion
  • TMF648 — Open API: Quote Management
  • TMF680 — Open API: Recommendation
  • TMF634 — Open API: Resource Catalog Management
  • TMF664 — Open API: Resource Function Activation and Configuration
  • TMF639 — Open API: Resource Inventory Management
  • TMF652 — Open API: Resource Ordering Management
  • TMF685 — Open API: Resource Pool Management
  • TMF633 — Open API: Service Catalog
  • TMF638 — Open API: Service Inventory Management
  • TMF641 — Open API: Service Ordering Management
  • TMF645 — Open API: Service Qualification
  • TMF657 — Open API: Service Quality Management
  • TMF653 — Open API: Service Test Management
  • TMF684 — Open API: Shipment Tracking
  • TMF663 — Open API: Shopping Cart
  • TMF623 — Open API: SLA Management
  • TMF621 — Open API: Trouble Ticket
  • TMF677 — Open API: Usage Consumption Management
  • TMF635 — Open API: Usage Management
  • TMF672 — Open API: User Roles & Permissions

message

A web service endpoint is an entity, processor or resource where interaction messages can be targeted.

Message information headers convey end-to-end message characteristics, including addressing for source and destination endpoints, as well as message identity.

Application layer protocols provide a modular packaging model and mechanisms for encoding data within modules.

Lightweight messaging protocols are not concerned with service metadata, data interchange formats or application semantics.

Asynchronous messaging is used for reliable transfer.