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
Imagine if your backend had no infrastructure. No permanent server, nowhere for your API to call home. Sounds a bit bleak, doesn’t it? As it turns out, serverless backends could be the next big thing for implementing truly scalable cloud architecture. Read more
Humpty Dumpty sat on a wall,
Humpty Dumpty had a great fall.
All the king’s horses and all the king’s men
Couldn’t put Humpty together again.
That sure sounds like the last time your site went down and every team in the office started panicking, right? 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
How many organizations are adopting an API strategy in Helsinki? Quite a few — for one, Helsinki arguably is the most successful city in the world using open data, with an active developer portal (Dev.Hel.fi) enabling the creation of new applications on top of city data to promote participatory democracy. Read more