Blog

- September 23, 2016

hero-book-blogAPI Developer Weekly – September 22, 2016 – Issue #129
A hand-curated weekly newsletter for API developers, published with permission from LaunchAny and CaseySoftware.

Subscribe to their newsletter to stay updated on the latest API trends and industry news.


Hot Topics
Just Because Github Has a GraphQL API Doesn’t Mean You Should Too
New advances are constantly made to the fundamental architecture of networkable APIs drawing into question the longevity of the prevailing approach. Like how RPC-style APIs gave way to REST-styled APIs. Now there’s GraphQL from Facebook and its recent adoption by Github raises interesting questions. [programmableweb.com]

HTTP APIs and Hypermedia
I have been trying to finish this blog post forever, and the motivation was sparked by a tweet from Spring’s Oliver Gierke, thanks a lot ! @olivergierke in brief : We like service registries because we do RPC. We care less about hypermedia because actually we don’t do REST. [michaeltecourt.github.io]

Decouple User Identity from API Design to Build Scalable Microservices
How does one go about securing APIs, microservices, and websites? One way to do this is by focusing on the identity – knowing who the caller is, and what the caller is allowed to do with your data. Too often, though, providers rely too heavily on user social identity, pairing it way too closely with the design of their APIs. by Bill Doerrfeld [nordicapis.com]

Building Hypermedia APIs with HTML
Summary Jon Moore discusses the pros and cons using HTML for an API media type, as well as the particulars of implementation patterns, from representations to building programmatic HTML clients. Dr. Jon Moore is a Technical Fellow at Comcast Corporation, where he manages the software architecture for the company’s consumer-facing web and mobile applications, which serve billions of requests per month. [infoq.com]

Introducing wicked.haufe.cio
As you will have noticed over the last year or so, we are currently working on making our company composable and flexible, and a main building block of that strategy are APIs as enablers. There are quite some solutions for API Portals. So, why did we (in parts) roll our own? This blog post will try to shed some additional light on what led to this… [dev.haufe.com]

HTTP Calls in Ruby
An API doesn’t exist on its own. There are always two parties involved: The Client and the Server. In Rails, our apps are often the ones acting as the server, and we typically know how to troubleshoot the issues that inevitably arise. by Leigh Halliday [blog.codeship.com]

Writing technical user stories
Recently I gave a talk about writing technical stories and ways I have found to slice user stories thinner at Product Camp Toronto. I thought it’d be good to share some ideas from that talk here as well. [onproductmanagement.net]

A New API Programming Language SDK Icon Set
I quickly came across Devicon, a set of icons representing programming languages, designing & development tools which you can use as a font or with SVG code. At the Github repo for the project, it says they have 78 icons with over 200 versions total. [apievangelist.com]

APIs are a Battlefield by Shelby Switzer
An interactive presentation created with Slides. [slides.com]

The Five API Monetization Models – Rob Zazueta, RESTFest 2016
A truly successful API is one that drives the goals of the business. And what is the primary goal of every business? Making mad stacks of $$$ y’all. In this ta… by Rob Zazueta [slideshare.net]

Emacs as REST client
Emacs as REST client Editor wars! Kirk Fort DevOps, Servosity [docs.google.com]

APIStrat Boston 2016 – Nov 2-4
APIStrat Boston – under the direction of our 2016 Program Chair Lorinda Brandon – is already shaping up to be our best program ever. Our three days of workshops, keynotes, fireside chats and speaker sessions 2016 reflect the maturity and diversity of the API business and community today. [boston2016.apistrat.com]

API Digest #53: What if Developers Aren’t Meant to Do API Design?
We are continuing the API Digest series. As always, we begin with the list of topics mentioned in this issue: The API Stylebook Three keys to design-time governance Headlines that condemn APIs are written for clicks Internal API design for distributed teams What if developers aren’t meant to do API design? [api2cart.com]

Upcoming Web API Events
A list of upcoming Web API Events, maintained by Matthew Reinbold


The Business of APIs

Shippo raises $7 million to further its goal of being Twilio for shipping
Shippo announced today that it has raised $7 million for its shipping for business platform. The investment in its Series A was led by Union Square Ventures and will be used to develop the company’s API and dashboard, onboard more carriers, improve functionalities, and allow it to begin crafting a recommendation engine it hopes will help customers “ship smarter.” by Ken Yeung [venturebeat.com]

The PSA Peugeot Citroën’s APIs
Making vehicle data, events and notifications makes sense to me when it comes to vehicles and APIs, and is something that seems like it should just be default mode for all automobile manufacturers. The correlation API seems in a different category, and elevated to more of an innovate class, beyond just the usual car activity. [apievangelist.com]

Using IFTTT (IF This Then That) to Extend API Alert Messaging
IFTTT (IF This Then That) is a site that enables the creation of API “Recipes for the Small Business Owner.” Activity that takes place on a particular site is monitored by IFTTT, and if a trigger event occurs, then an action can be initiated that produces a result on a different site. by Kevin Farnham [apiscience.com]

A Twilio Process To Emulate Within Your Own API Operations
Forgive me for just copying and pasting this much from your story Gordon, but I think it needs isolation as its own story. This is the approach to designing, developing, and operating APIs that companies need to hear more about. These are the technical product development benefits which being API-first can bring to the table. [apievangelist.com]


(Un)Related Topics

12 Fractured Apps
Over the years I’ve witnessed more and more people discover the 12 Facter App manifesto and start implementing many of the suggestions outlined there. This has led to applications that are far easier to deploy and manage. However practical examples of 12 Factor were a rare sight to see in the wild. by Kelsey Hightower [medium.com]

Google’s new acquisition makes building chatbots easier
Google took a shot at Facebook’s chatbot-building services on Monday with its acquisition of API.ai, a company that helps developers build and improve conversational interfaces for their services. API.ai has more than 60,000 developers using its platform to create conversational user interfaces for apps like Slack, Facebook Messenger and Kik. by Blair Hanley Frank [computerworld.com]

Tuning NGINX
While NGINX is much younger than other web servers, it has quickly become a popular choice. Part of its success is based on it being the web server of choice for those looking for a lightweight and performant web server. by Ben Cane [blog.codeship.com]

ThursdayBram.com – What Writing Fiction Will Teach You About Writing Documentation
I gave this talk at Write the Docs this morning and wanted to share my slides. They’re embedded below, but you can grab a PDF here and a link to a Google Drive version with my notes here. [thursdaybram.com]


Want to share something?
As always, if you want to chat, share a link, or make a suggestion, feel free to drop us a quick note using Twitter (@launchany and @caseysoftware) or by emailing us at: james@launchany.com.