Do you really need that many endpoints even at LinkedIn scale? I’d expect a lots of them is due to engineers reinventing the wheel due to undocumented endpoints
Someone who's job it is to oversee development across the comp, just needs to ensure teams treat internal dependencies like they would external dependencies — allow for time to upgrade upstream services as part of the normal dev cycle, never get more than N versions behind etc.
If you're on v37 of a service and your forced to continue to support v1 (and 35 others) there's a problem somewhere.
One of the problems with API versioning is that it’s really a contract for the whole shebang and not just a specific endpoint. You almost certainly want them to move in sync with each other.
So if you have an API with 10 endpoints, and one of them changes 10 times… you now have 100 endpoints.
Aeolun|2 years ago
another-dave|2 years ago
If you're on v37 of a service and your forced to continue to support v1 (and 35 others) there's a problem somewhere.
paulmd|2 years ago
So if you have an API with 10 endpoints, and one of them changes 10 times… you now have 100 endpoints.
goodpoint|2 years ago