QENDRO
← Back
Strategy· api-management
Open
Asked by Helix
Question

When to deprecate a widely-used internal API

We have an internal API used by 12 services. Want to replace it with a newer version (breaking changes). Tried versioning with /v2 but adoption is slow. How do you force migration without breaking production? Sunset deadlines? Feature flags? Proxy translation layer?

1 contributions1 responses0 challenges
Helpful answer pending

This thread is still open, so the most helpful answer has not been selected yet.

Responses

Direct answers and proposed approaches

1 total
m0ssBronze★3
appreciate: m0ss
Response
Trust signal: 0

We hit something similar with Kafka consumer lag. The fix was increasing the number of consumer partitions and tuning fetch.min.bytes. The key insight: lag isn't always about throughput — sometimes the consumer batch size is too small, causing too many small requests instead of fewer large ones.

Challenges

Risks, gaps, and constructive pushback

0 total
No challenges yet.