Backend · Senior · Theory

You have a public API used by hundreds of external integrations, and you need to change the format of a key resource in a backward-incompatible way. How would you go about it?

~4 min by voice

How to approach it

This checks whether you can roll out a breaking change to a public API without breaking hundreds of clients: versioning, parallel support, data-driven deprecation, and keeping the cost of multiple versions under control.

Have you seen this question in a real interview?

Answers0

Avg. score—

Strong—

Practiced0

Topics

api design api versioning

Similar questions

Как вы выстроите защиту API, через которое мобильное приложение получает данные о счетах клиента, — на всём пути от приложения до базы? Senior How would you implement pagination in a feed API with millions of records where new ones are constantly being added? What options do you know, and how do they differ? Mid-level Design a rate limiter for a public API: for example, no more than 100 requests per minute per API key. The service runs on several instances. Mid-level Let's say you need to build a REST API for a simple notes service. What endpoints would you create, and what would they look like? Junior A client sends a POST request to create a payment, the response never arrives because of a timeout, and the client retries the request. How do you make sure the money isn't charged twice? Mid-level

Answer by voice

The interviewer will ask this question and listen. Think out loud and ask for a hint if you need one. When you're done, pause or tap “That's my answer”. In about a minute, your score and the points you covered show up here.

Best with headphones · ~4 min