Backward Compatibility
The ability of a newer version of a protocol or system to work with older versions without breaking existing functionality. HTTP/2 maintains backward compatibility with HTTP/1.1 semantics (methods, status codes, headers). gRPC uses Protocol Buffers with field numbering to ensure older clients can parse newer messages. Breaking backward compatibility forces coordinated upgrades and is generally avoided in protocol design.
관련 프로토콜
가이드에서 언급됨
API Versioning Strategies: URL, Header, and Query Param
API Design & Best Practices
Migrating from HTTP/1.1 to HTTP/2
Migration & Upgrades
Migrating from REST to gRPC
Migration & Upgrades
Migrating from WebSocket to Server-Sent Events
Migration & Upgrades
Migrating from TLS 1.2 to TLS 1.3: Configuration and Compatibility
Migration & Upgrades