|
|
|
|
|
|
by NathanKP
3355 days ago
|
|
|
A classic example that I've encountered would be using some custom web socket RPC protocol for communication between microservices instead of just using plain HTTP. It can be tempting because an engineer thinks "I can optimize this and reduce the network overhead using this creative protocol." But now they have put themselves in a situation where if anything in that custom protocol changes they will have to update every single microservice in their backend ecosystem. |
|
|
This is just API versioning, that needs to happen regardless of the protocol you choose.
edit I see you mean the protocol itself (like if gRPC goes from version 1 to 1.2 or something). Yes, that's a thing... most protocol developers are careful about backwards compatibility to allow for some services to be behind a few minors to account for this. Also, HTTP still isn't invulnerable to this...HTTP/2 is very much a thing.