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
“Build it and they will come” is certainly not the case in the API world. Even if you have a functionally brilliant service, without the right positioning your conversion rates could still be very low. Assuming you’ve made your developer program visible to the public, how should you then promote your API? Read more
DevOps is the set of tools, processes and activities that modern software development teams put in place in order to ensure that they can convert code into live applications in a stable and repeatable way. It’s a bit of a catch-all term, and can be broken down into different areas. Read more
Continuous Integration (CI) is a part of the DevOps process that aims at integrating code written by a team of developers. This involves building the code along with dependencies, testing it against a prepared set of unit and integration test suites, and creating reports listing the resulting artifacts. Read more