From the course: Planning a Versioned RESTful API with Claude
Join today to access over 25,300 courses taught by industry experts.
Version strategy overview - Claude Tutorial
From the course: Planning a Versioned RESTful API with Claude
Version strategy overview
- [Harit] As you know that we have book which has 17 fields, which means 17 pieces of information associated with a book. But as designing APIs, we must keep things in mind that everything changes over a period of time. So let's say we have 17 fields today, and let's say your developers have implemented that and it's in production. But tomorrow there is a new field that we want to add, which is number of copies sold. And now we have a problem. Why? Because we have certain set of publishers who are using existing endpoint in production, but there are other publishers who want to also send and use this additional piece of information, which is number of copies sold. So then the question becomes, how do you keep the same endpoint behaved differently? And that's where the idea of versioning comes in. So the publishers in first case, are using V1 version of the API. And publishers on the other side are using version two, which is the next version of the APIs. But then the question is, how…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.