At Teads, for more than two years, we have been migrating our business logic to a central component. This component exposes an API that is consumed by tens of services (BFF, cron jobs, AWS lambdas…) and also engineers via a command-line interface.
Our industry is moving quickly and so is our API. Every week, new endpoints are created and the existing ones are updated. Every day, the component serving the API is deployed several times. Not breaking clients is obviously a necessity. We have chosen gRPC as a protocol, for the backward-compatibility features and the strong contractual guarantees it brings.