The Latest News On The API Economy
Searching: No Search Term , Filtered By Article Type: "Elsewhere on the Web"
Limiting API usage is a standard technique to avoid overloading your server or database at critical times. It’s not always so easy to manage without annoying API clients. Ben Weintraub over at the New Relic blog explains the techniques the analytics company developed to limit resource usage.
These days microservices are often pursued because tech giants like Uber and Twitter use them. Adam Drake argues that your startup probably doesn't need them and that they should only be used when your monolith gets so complex making the app more modular won’t cut it.
Akamai has made improvements in its API documentation since its early days. Mike Sierra, technical writer at Akamai, explains how they improved the accuracy of their API docs in recent years. In the early days, developer teams were in charge of different parts of the documentation.
With Alexa’s growing popularity, developers across the world are building skills to connect the Amazon device with smart home devices through the smart home skill API or a custom model. Amazon has seen issues with some submissions for skill certification.
REST and JSON are the bread and butter of developers creating web APIs. Once apps reach a certain size, though, the lack of type safety and other issues start to grate. Michal Witkowski and Marcus Longmuir over at Improbable explain how they learned to stop loving REST and move to gRPC.
Microservices look like a universal solution to all the problems of managing a large monolithic app. However, software legend Martin Fowler recommends holding your horses. You shouldn’t even consider using them unless your team has some core competencies. He explains what they are over at his blog.
Too many people don’t know the difference between OpenID Connect and the OAuth 2.0 specifications. This results in devs publishing insecure apps because they’re using an ID token to secure the API where they should be using an access token. This article helps explain to you the difference.
When you break your monolith up into microservices connected by exposed APIs, you expect these services to be decoupled and independently releasable. But too often they still aren’t. Jose Luis Ordiales Coscia over at the Klarna blog explains how to fix this problem with the robustness principle.
A few years ago when Brigham Young students wanted to create a site based on university data, they were forced to scrape the university's website. Now BYU has launched a university-wide API and is about to launch a developer portal. David Raths explains what the future holds for APIs at BYU.
We all know you should make your API backward-compatible. But how about forward-compatible? Being careful to make sure your API design will be consistent with future changes that you don’t know you’ll make yet. Adam Bar gives you eight steps he’s learned in order to make it a reality.
Creating an API that is easy to use and maintain is difficult. Hootsuite took some wrong turns at early stages and have made great strides since then so that they can offer an API that’s fast, easy-to-use and easy to maintain. The Hootsuite blog explains what lessons the company has learned.
There are three standard ways to manage API authentication these days: API keys, OAuth tokens and JSON Web tokens (JWT). Adam Duvander over at the Zapier engineering blog explains how and when to use them. The humble API key is the common and earliest form of API authentication.
It’s no secret that APIs are becoming vital to businesses’ success. But there’s still a secret as to how to have success with APIs. A new study from CA Technologies asked 1,770 large enterprises across the world what they’re doing with APIs and got some insight into who has success and why.
A researcher has found a vulnerability in the latest version of reCAPTCHA that could let spambots bypass reCAPTCHA fields across millions of sites. The developer has a script that uses Google’s speech recognition API to solve audio challenges associated with the latest version of reCAPTCHA.
Global cloud API revenues are expected to grow dramatically in the next few years thanks to businesses’ growing dependence on cloud computing. That’s according to a new report by Persistence Market Research. The NY-based research firm predicts global revenues will soar to $1.78bn by 2026.
It’s never been easier to create an API. With Web frameworks like Flask and Express and app engines like Heroku, you can get an API up and running in hours if not minutes. The downside to this is that the easier it is to build an API, the more badly designed APIs there are going to be.
There are more programming languages these days in production environments than you could learn in a lifetime. So which should you choose to make sure you’ll always be an in-demand developer? Jay Patel at Coding Dojo gives you the low-down on the top 9 programming languages to learn in 2017.
Serverless frameworks, despite their name, are not really serverless. Of course, there are servers somewhere handling requests but you don’t have to worry about them. You just post a snippet of code and your hosting service takes care of the rest. But who could benefit from these frameworks?
Many of Intuit’s APIs have been going a couple of years but their success has turned heads. Mark Boyd over at Vision Mobile sat down with Intuit’s Ketan Kittur, director of project management and partnership integrations, to understand how the company makes sure its third party devs are successful.
It’s no secret that adopting APIs is good for business. But players in some of the largest traditional industries, specifically energy, logistics, packaging and banking, have been slow to catch on. Mark Boyd over at Network World explains how they lag behind the rest and why it matters.