Copy
The week in API strategy, news, articles, and upcoming events.
James Higginbotham, Curator  A hand-curated weekly newsletter for API developers, sponsored by LaunchAny and CaseySoftware

Find this via Twitter? Subscribe now so you don't miss out
 
 

API Developer Weekly

Oct 17, 2019 - Issue #281
This week's assortment of articles includes a great piece from Matt McLarty on why GraphQL seems to bring out so much emotion, how HTTP 2 and 3 will change the way we design and interact with web-based APIs, and 3 lessons from DevRel experts. There is also some great content toward the bottom regarding Apache Kafka and some insights for observability. Happy reading! -- James
 
Hot Topics
Why is everyone so emotional about GraphQL?
GraphQL offers a new style of API design intended to provide API consumers with unified access to back-end data and services. In spite of this seemingly universal aim, GraphQL has created a schism in the API community between those who believe it is superior to state of the industry RESTful API design and those who [...] by Matt McLarty [blogs.mulesoft.com]

How Multiplexing Changes Your HTTP APIs
When I first learned about SPDY, I was excited about it for a number of reasons, but near the top of the list was its potential impact on APIs that use HTTP. [mnot.net]

3 Lessons from DevRel Experts on Building Developer Communities
This week, we brought together a panel of developer community experts from Devada, Weaveworks, RingCentral and IBM to discuss their experiences creating and running developer communities. Moderator Jesse Davis, EVP of Product and Technology for Devada, led a great conversation about how devtools teams can engage with and foster the communities that grow around their products. [heavybit.com]

The difference between resources, endpoints, objects, and items in the bunq API documentation
As a developer, you must have browsed dozens of API documentation websites and noticed that nomenclature might differ from one site to another. In our docs and blog articles, we use our own version of common API terminology that is mostly universal but still might be confusing or unknown to some of our readers. by bunq [medium.com]

Kubernetes API Vulnerable to Billion Laughs Attack
Recent reports show that the Kubernetes API is vulnerable to the billion laughs attack. The attack is a specific type of DoS attack targeting parsers. The vulnerability in the Kubernetes environment occurs within parsing YAML manifests. The apiserver does not validate or limit such manifests. [programmableweb.com]

How to build a Google Maps Platform integration with deck.gl | Google Cloud Blog
That's all there is to it. You've built your first deck.gl data visualization using data from one of Google Cloud's BigQuery public datasets. If you ran into any issues, you can also refer to the code in scatterplot.html to see the final code of this tutorial. [cloud.google.com]

API Traffic Management 101: From Monitoring to Managing and Beyond
Mike Amundsen introduces developers and network administrators to the basic concepts and challenges of monitoring and managing API traffic. [nginx.com]
  
The Business of APIs
Why is API key to your business? | Contact Center Software | ziwo.io
API is the acronym for 'Application Programming Interface,' which is a software intermediary that allows two applications to talk to each other. Each time you use an app like Facebook, send an instant message, or check the weather on your phone, you're using an API. [ziwo.io]
 
(Un)Related Topics
Don't build systems. Build subsystems.
Always consider your design a subsystem.Jabe Bloom When we build software, we aren't building it in nowhere. We aren't building a closed system that doesn't interact with its environment. We aren't building it for our own computer (unless we are; personal automation is fun). We are building it for a purpose. by jessitron [blog.jessitron.com]

dunglas/vulcain
Use HTTP/2 Server Push to create fast and idiomatic client-driven REST APIs - dunglas/vulcain by dunglas [github.com]

Reality Check: 6 Cost-Benefit Considerations When Adopting Microservices - The New Stack
For those who want to better enable legacy applications to be assets - rather than speed bumps - in your digital journey, the idea of adopting microservices can be exciting and sobering simultaneously. Adopting a microservices architecture is similar to embracing any other new technology or software discipline: you need the appropriate environment and staff. by Hans Otharson, Chris Grams, Freyja Spaven [thenewstack.io]

Microservice Observability, Part 1: Disambiguating Observability and Monitoring
"Pets versus cattle" has become something of a standard vernacular for describing the shift in how we build systems. It alludes to the elastic and dynamic nature of these (typically, but not necessarily) container-based systems with on-demand scaling and more transparent fault-tolerance. I've talked before about this transition before and specifically how it relates to monitoring. by Tyler Treat [bravenewgeek.com]

How LinkedIn customizes Apache Kafka for 7 trillion messages per day
The most important question to answer here is whether to choose the Upstream First route or LinkedIn First route (shown as "Commit to upstream first?" in the flowchart). Based on the urgency of the patch, the author should carefully assess the tradeoffs of both approaches. by Jon Lee [engineering.linkedin.com]
 
Useful Resources
Upcoming Web API Events
A list of upcoming Web API Events, maintained by Matthew Reinbold

Tyk Whitepaper: Approaching your API Strategy
As well as writing for the James Higginbotham is an Executive API Consultant with experience in API strategy and software architecture. James guides enterprises through their digital transformation journey to deliver a great customer experience and provides training in API and microservice design. [content.tyk.io]


Book: A Practical Approach to API Design by Casey and Higginbotham
If you read the tech press, everyone knows they need an API but most aren't really sure what it is. They treat it as another checkbox like "Web 2.0" was a few years ago or a mobile app was most recently. In fact, there’s an entire “API-first” movement in development circles that most people don’t understand or even realize why. In this book, we'll start by discussing the what an API is, why you might need one, and follow up with the how to build one. [leanpub.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 or tagging us on Twitter (@launchany and @caseysoftware) or by emailing us at: james@launchany.com
 
Follow on Twitter    Forward to Friend    Subscribe
Copyright © 2019 LaunchAny, All rights reserved.
unsubscribe from this list