API Digest #66: Where API Management Is Headed in 2017?
We are back with the traditional fortnight API Digest, and, in this issue, you are going to see a wrap-up of the following articles:
- Three common API design mistakes and how to overcome them
- Where API management is headed in 2017?
- Google released an API design guide recently
- A simple way to implement rate limiting
- HTML API: what they are and how to design a good one
- Gartner clarifies where the API Economy is heading
- Liberating operational data from a legacy system
Many of us wonder where API management is headed in 2017. David Chiu expects to see API management solutions deliver integrated functionality across the API lifecycle and double down on security, orchestration, and developer enablement.
Google released an API design guide recently, which is pretty straightforward in its purpose, with a goal of helping "developers design simple, consistent, and easy-to-use networked APIs." Look what Kin Lane has to say about it.
Jason Harmon, head of APIs at engaging forms tool Typeform, recently gave a talk on three common API design mistakes and how to overcome them. Included are the use of HTTP POST versus GET, compressing APIs that poll a lot and using group calls to take advantage of common chains of calls.
Before we heard about API and before its growth inside organizations, one of the main reasons to implement rate limiting was to defend applications against DoS attacks. Nowadays, with the advent of API and its increasing popularity, rate limiting has been replaced by throttling. In his article, Roberto Picanco shows a simple way to implement rate limiting (throttling) and how things work in the background.
The API is at the heart of the technology of every connected person's daily life. Mark O'Neill, research director at Gartner, presented some of the trends in the API industry at a recent APIDays conference. In the article “Gartner clarifies where the API Economy is heading”, Jennifer Riggins delves into API industry trends and how they affect the future of the tech industry as a whole.
Liberating operational data from a legacy system is a challenge that lots of city governments face, and it strikes Mark Headd that there are some common lessons that can be derived from cities that have gone down this road already for those that are still trying to figure out the right approach.
See you in a fortnight! In the meanwhile, send us article suggestions and ideas. Either way, we are happy to hear from you. :)
P.S. In case you’d be interested in trying API2Cart, you can create an account and see how the API works on live stores.