The Latest News On The API Economy
Searching: No Search Term , Filtered By Article Type: "Elsewhere on the Web"
Software development has moved quickly in only a decade. From deploying to physical servers, to virtualization, and IaaS to PaaS. The latest development, however, is the Micro API, which builds on serverless computing and FaaS to take API development to the next level.
Lego is not the first thing product owners would think of when looking for a model onboarding process. But they should. At least that is Cristiano Betta’s theory over at his blog, who will tell you the lessons you can learn for your API from the Lego onboarding experience.
From Slack integrations to coffee buttons, if Starbucks were to open up their API to the public, there are a ton of integrations that third-party developers could create. Tendigi CTO Nick Lee over at the Tendigi blog couldn’t wait so he reverse-engineered the Starbucks mobile app.
AWS is running scared of Kubernetes as it becomes the industry standard for managing containers. Why? The open-source platform gives companies a way to run apps across different clouds not just on AWS. Matt Asay over at Tech Republic provides the details.
Consumers are interacting with retailers through an ever increasing range of channels. New channels are emerging all the time and a retailer that wants to stay ahead of the game needs to adopt an API-ready approach to make integrating those new touchpoints quick and painless.
In order to develop a REST API in PHP quickly and easily it might be a good idea to use a lightweight PHP framework. Developing your own from scratch with plain PHP, apart from being a pain and taking too much time, is likely to require a lot of testing and deviate from REST standards.
REST APIs use URIs to address resources. While they’re known as opaque identifiers, there are better and worse ways to write URIs. Guy Levin over at RestCase has formulated a set of design rules for API URIs that you should keep in mind to make things easy for your API clients.
Working with numerous third party APIs can be a headache. Damon Swayn of InSite should know. The InSite team has integrated countless APIs for its clients’ CRMs into its platform. Damon over at his Medium blog gives you the top four lessons he and his team have learned.
We keep hearing about alternative uses for blockchain tech beyond that of a currency replacement. But real-world implementations that prove such horizontal applicability are few and far between. Looking to plug a loophole in the short-selling of stocks, Overstock CEO Patrick Byrne has launched t0.
APIs sometimes go through changes that are so big they require a new version to make sure API users don’t break their apps. Versioning APIs is, however, difficult and some teams go out of their way to avoid it. Google can’t do that and so they’ve developed some consistent rules for versioning APIs.
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.