The internet is fundamentally an unsafe place. For every service, every API, there are users who would love nothing more than to break through the various layers of security you’ve erected.
We’ve previously discussed best practices when it comes to designing an API with quality developer experience. But what will the long term operational repercussions be for the design moves we make now?
For example, if URLs are designed without metadata to describe actions, later on, product owners will have a difficult time staring at unintelligible logs. Read more
Web APIs have been around for a long time now. While that means there’s a lot of great tools from a lot of amazing developers, it also means that, as a community, the API space has held on to some practices for a long time — some would argue too long in many cases. Read more
If you’ve been paying attention to the API space over the last year, you won’t be surprised to hear that there has been a lot of movement amongst companies that provide API-related solutions.
The most noteworthy example is Google’s $625 million acquisition of API platform provider, Apigee, in the fall of 2016. Read more
Recently, there has been debate over what the best practices are for versioning an API. Many public web APIs are retired as new versions replace them, but if you were to ask Roy Fielding, creator of REST, he may tell you not to version your API at all. Read more