Service API Patterns, Protocols, Coupling Types, Metrics > Service API Design Patterns > Canonical Protocol

 

Canonical Protocol

How can services be designed to avoid protocol bridging?

When services and consumers are designed to use different communication protocols, they may not be able to exchange data without the application of the Protocol Bridging pattern, which can introduce the need for undesirable runtime protocol conversion processing.

With the application of the Canonical Protocol pattern, the technology architecture is designed to limit enablement of cross-service interaction to a single or primary communications protocol or protocol version. All other technologies associated with supporting the protocol’s underlying communications framework are also standardized. This guarantees baseline technological compatibility across services.

 

 

 

 

 

 

 

 

 

 

 

Though still delivered by different projects via different vendor platforms, these services conform to one centralized communication protocol, making them technologically compatible.