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
It’s a universal truth that testing for errors, and debugging any that show up, isn’t a fun process.
Almost all API providers are familiar with the process of monitoring and testing. Before you commit code, API behaviors must be thoroughly vetted, as with any software release. Read more
One of the most important systems an API developer can implement is a system of monitoring. API implementation is not a “fire and forget” affair — continual support and development is necessary for a healthy, effective implementation, and this of course requires testing and monitoring. Read more
Since GitHub integrated ChatOps into their operational strata, the concept has garnered a good deal of excitement. Essentially, ChatOps moves system operations into a group chat room, enabling developers to collaborate, initiate tests, deploy software, and build a company culture all from a single unified command line. Read more
According to The State of API Survey Report 2016 by Smartbear, nearly 85% of the respondents agree that API quality is crucial to their organization. The same survey identifies the top three reasons keeping organizations from delivering quality APIs are:
1) Increased demands for speed
2) Lack of integration between tools and systems
3) Managing expectations of different stakeholders
A remedy for the first reason can be found by fine-tuning architecture and optimizing code. Read more