CW Developer Network

Oct 9 2018   7:13PM GMT

Postman assesses state of the Aye-Pee-Eye (API) nation

Adrian Bridgwater Adrian Bridgwater Profile: Adrian Bridgwater

Tags:

Application Programming Interface (API) development company Postman has conducted a state of APIs survey.

Well, an API dev tools company would, wouldn’t it?

Questioning its 5 million community members — but presumably not getting responses from ALL of them — Postman says it wanted to understand the API developers’ workflow, pain points and perspective for where the API space is headed.

Most notably, while microservices remain the most ‘exciting’ technology for API developers, the rise of containers and serverless architecture have emerged as the new favourites for this group.

Postman’s co-founder and CEO is bold enough to suggest that the data his team have collated might be able to help technical leads identify current norms within their technologies and where development teams need to focus their time and energy.

The survey results suggest that nearly two in three API developers spend a quarter of their week working with APIs.

Also here, the majority of API knowledge is gained on the job or from online resources, while published API documentation and online communities also contribute heavily.

Aye-Pee-Eye?

Additionally, the Postman community were asked how they pronounce API, with an overwhelming 82% saying that they use “Aye-Pee-Eye” – but another 12% said “Appie” (as in rhymes with happy).

Finally, developers shared a clear preference in the Star Wars vs. Star Trek debate. A whopping 76% of API developers identified as “All Star Wars” or “More Star Wars than Star Trek”.

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

Share this item with your network: