Menu

API Versioning: How to Evolve Your API Without Breaking Existing Clients
πŸ“°

API Versioning: How to Evolve Your API Without Breaking Existing Clients

DEV Community: backendΒ·Odumosu MatthewΒ·about 4 hours ago
#LJnBK5zy
#devtobackend#devto#dev#socket#works
Reading 0:00
15s threshold

πƒπšπ§π’πžπ₯ π₯𝐚𝐧𝐝𝐬 𝐒𝐧 π‘π¨π¦πž 𝐟𝐨𝐫 𝐚 𝐜𝐨𝐧𝐟𝐞𝐫𝐞𝐧𝐜𝐞. 𝐏𝐑𝐨𝐧𝐞 𝐚𝐭 4%.

He reaches the hotel, pulls out his charger, and stops.

The plug doesn’t fit the socket.

Nothing is broken. The phone works. The socket works. They just no longer speak the same shape

Software has the same problem every day.

A team improves their API. They rename a field, change a format, remove something β€œnobody uses.” It works perfectly on their side.

Then thousands of people who haven’t updated their app open it on Monday morning, and it stops working. Payments fail. Screens go blank. Support lines fill up.

The new socket was better. It just didn’t fit the plugs already out in the world.

Good engineers know that once an API is public, it becomes a promise.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.