API Digest #56: APIs: Worth Getting Fired over?

Published 31 October 2016 | Updated 24 October 2019 |

api digest 56

On the threshold of Halloween, we have prepared for you some interesting API stories. So sit for a spell, have some brew and enjoy our fresh API Digest. This time you will read about the following matters:

  • What does it mean to monitor a Web API?
  • APIs: Worth getting fired over?
  • Why webhooks provide a really efficient alternative to API polling
  • No REST - architecting real-time bulk async APIs
  • API technology does not have to mindlessly march forward
  • Enterprise augmented reality: AR applications are just around the bend
  • API versioning with the Semantic Versioning specification

In the article “APIs: Worth getting fired over?Annie Turner explains why it is essential to ensure APIs are embedded in your business strategy and managed as a strategic asset, whether you’re a startup or incumbent, a multinational or a government department, a digital health, Internet of Things/Everything (IoT/E) or smart grid provider.

There are few systems today that aren't making use of at least one Web API to outsource complex functionality like payments, mapping, or notifications. However, there is a large gap in terms of how we monitor these inherently failure-prone additions to our business apps. So what does it mean to monitor a Web API? Christopher Young provides the answer from the customer’s and provider’s perspectives.

Dislocated Shoulder

I dislocated my shoulder yesterday and rushed to the hospital. After I got necessary treatment and recommendations of the doctor, I went home and asked myself: how soon will I recover enough to be able to play the guitar again? This page gave me all answers.

At QCon New York 2016, Michael Uzquiano talked about architecting real-time bulk async APIs. Watch the video presentation to learn how to evolve the Evolution of REST over HTTP to transactional, asynchronous bulk operations. Michael Uzquiano also covered job descriptors, workers, the job queue and scaling workers across an API cluster elastically.

Dawn Foster believes that “webhooks provide an efficient alternative to API polling”. They are not just a convenient way to inform users of new events, webhooks are also a way for sites to maintain stability.

Though willing to keep an open mind when it comes to microservices, DevOps, GraphQL, voice, bots, drones, and the other technological frontlines, API Evangelist believes that API technology does not have to mindlessly march forward.

Stan Gibson examined the potential of augmented reality for enterprise. In the article, he covers productivity gains, industries, use cases, and best practices of utilizing augmented reality technology.

Zachary Flower has explained why it is good to version API with the Semantic Versioning specification. He believes that the Semantic Versioning specification is not just a great tool to improve efficiency and reduce ambiguity within your organization about application versioning. It is also a great way to give your application and your users the respect they deserve.

For more API news and insights, read API developer weekly #131 and #132 by Keith Casey and James Higginbotham.

Have a spooktacular Halloween! 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.