People.
There is a difference between a backend and an API.
Taking the endpoints that you wrote for your site, slapping some documentation on them and publishing it
does not make an API.
There is a difference between a backend and an API.
Taking the endpoints that you wrote for your site, slapping some documentation on them and publishing it
does not make an API.
An API needs designing. It needs a conscious language and consistent conventions.
Standard auth.
Paging.
Careful error codes and messages.
Versioning.
Standard auth.
Paging.
Careful error codes and messages.
Versioning.
A backend is whatever your front end needs. It should change when your front end needs it to change.
Don’t restrict it to historical behavior because other systems have grown dependent on it.
Don’t restrict it to historical behavior because other systems have grown dependent on it.
Don’t publish your back end to some catalog!
Not every HTTP endpoint needs to be an API!
Boundaries, people!
Not every HTTP endpoint needs to be an API!
Boundaries, people!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
