Mufasa: Look, Simba. Everything the light touches is our beautiful, well-maintained code base.  Simba: But what's that shadowy place over there?  Mufasa: API V1, which still handles 95% of requests.
you are viewing a single comment's thread
view the rest of the comments
[–] 22 points 2 years ago (5 children)
location /old_api {
  redirect /new_api
}

(can’t be bothered to check the syntax).

  • source
  • parent
  • hideshow 5 child comments
  • [–] 19 points 2 years ago (4 children)

    If you have a major version change, it means that old API calls will break against the new API, assuming they are accurately following semver.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 2 years ago (2 children)

    A translation layer could be used, no? Check api version, translate any v1 specific calls into their v2 counterparts, then submit the v2 request?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)

    This isn't really efficient because when v2 gets updated now you have to update the translation layer as well.

    Any improvements you made in v2 would likely not translate.

    Essentially the best way is to provide users with an incentive to switch. Perhaps a new feature or more requests.

  • source
  • parent
  • hideshow 1 child comment