Explore >> Select a destination
|
You are here 
|
httptoolkit.com | ||
| | | | |
yos.io
|
|
| | | | | You're building an API. You develop a backend service with a few endpoints and deploy it to production. You publish several official language-specific API clients as well as an API documentation. The day ends on a happy note. The following day, a new feature is being added the API. You have to: Update the server implementation to support the new feature. Update all client libraries (one SDK for each supported platform and language.) Update the documentation. All the above must be consistent with each other. Also, the frontend team is blocked until your backend API is complete. You let out a heavy sigh. | |
| | | | |
bendauphinee.com
|
|
| | | | | ||
| | | | |
www.mnot.net
|
|
| | | | | For better or worse, Requests for Comments (RFCs) are how we specify many protocols on the Internet. These documents are alternatively treated as holy texts by developers who parse them for hidden meanings, then shunned as irrelevant because they cant be understood. This often leads to frustration and more significantly interoperability and security issues. | |
| | | | |
blog.fanout.io
|
|
| | | New to the subject of realtime APIs? This article is the place to start! We'll discuss the most common design approaches and their pros/cons, as well as link... | ||
