Java · Senior · System design

Your team is writing an internal Java library that twenty other teams will use. How would you design its API so it can evolve without breaking clients?

~10 min by voice

How to approach it

This checks whether you understand that every public element of a library becomes a permanent contract, and whether you can build the ability to evolve into the API from day one: hide the implementation, control extension, watch binary compatibility and retire old things carefully.

Have you seen this question in a real interview?

Answers0

Avg. score—

Strong—

Practiced0

Topics

oop api design

Similar questions

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 A client calls your create-payment endpoint, the response is lost to a timeout, and the client retries the request. How would you design the API so the money isn't charged twice? Senior

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 · ~10 min