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

Sept 8, 2022 - Issue #422
This week's articles take on a bit of a different perspective. First, we examine how software developers can improve their technical writing skills (something every developer needs to do). Nordic APIs takes a look at developer experience as a teaser for their newly-released guide. The IETF has posted a draft of a Resumable Uploads Protocol to recover from failed client-to-server uploads (anyone remember ZModem?). Plus, the (Un)Related section offers a spotlight on event driven architectures and asynchronous APIs. 

Happy Reading!
-- James
Hot Topics
A Software Developer's Guide to Technical Writing
The Economist once ran an advert asking for an article of scientific journalism to compete for an internship spot on its team. The company specifically said that it would rather have a scientist who could write than a journalist who knew some science. by David Eastman []

What Is Developer Experience?
We've just released a new eBook, Developer Experience ! Be sure to pick up a free copy for our top insights on crafting quality developer experiences. Below is the preface. Developer experience, sometimes abbreviated as DevX or DX, is similar to user experience (UX) but focuses on the experience developers have while using a software tool. by Bill Doerrfeld []

tus - Resumable Uploads Protocol
HTTP clients often encounter interrupted data transfers as a result of canceled requests or dropped connections. Prior to interruption, part of a representation may have been exchanged. To complete the data transfer of the entire representation, it is often desirable to issue subsequent requests that transfer only the remainder of the representation. []

Comlink | Superface
Comlink is description language for autonomous APIs. It allows you to declaratively describe your API integrations in a way that separates the design-time semantics from the run-time implementation details. In other words, Comlink allows for defining the words we use to describe the capability of an API separate from the details for implementing that capability. []

OAuth 2.0 (Introduction and Exploitation Part I) Explained
In this blog, I am going to explain how OAuth 2.0 works and what vulnerabilities can be raised if it is implemented incorrectly. []

GraphQL API design
API design refers to the process of developing application programming interfaces (APIs) that expose data and application functionality for use by developers and users. There are many different ways to develop such an API, we can use SOAP, REST, GraphQL, gRPC and others. []

Generated GraphQL Schemas and Schema Design
GraphQL is a type-safe language for APIs. A common misunderstanding is that GraphQL is another complete query language, like SQL, which allows you to search, filter, and select all the objects in a database. Instead, GraphQL should be thought of as a way to specify the types of data available and the specific operations users [...] []
Business of APIs
Google Introduces Pay-as-you-go Pricing for Apigee API Management
Recently Google introduced a pay-as-you-go pricing model for Apigee's API management to provide customers with more flexibility in using the service and control costs. With the new pay-as-you-go model, the company is providing customers with an additional pricing plan for the service, allowing them to only pay for what they use. []

Postman Launches Ecosystem Partner Program to Support Accelerated API-First Adoption
Postman, the world's leading API platform, today announced the launch of its Ecosystem Partner Program. This program will allow companies and independent software vendors (ISVs) to build joint solutions with the Postman API Platform to improve the developer experience and gain visibility across Postman's user base of over 20 million API professionals. []

The benefits and challenges of event-driven architecture
Data is increasing exponentially. The amount of data generated daily will reach 463 exabytes globally in three years. To put that in perspective, it is estimated that all of the words ever generated by human beings total five exabytes. by , James Aley []

McDonald's event-driven architecture: The data journey and how it works
By Vamshi Krishna Komuravalli, Director, Principal Architect andDamian Sullivan, Senior Manager, Software Development Last week, in the first of a two-part post, we explained how we implemented event-driven architecture in Global Technology. In this week's post, we explore how actually works and how the data flows through the system. by Global Technology []

Event Streaming and Event Sourcing: The Key Differences
Customers like to be aware of events when they happen. After a customer orders a new pair of shoes and receives a notification that the purchase has been shipped, getting up-to-the-minute shipping status updates before it arrives improves the overall customer experience. The updates about the order are events that trigger a response in an event-driven architecture (EDA). by David Dieruf []

API series - Push: REST easy, APIs transformed into streaming data feeds
Real-time data streaming and messaging solutions company Push Technology has enriched its Diffusion Cloud service. Described as an intelligent event-data platform, the additions include a new REST adapter and improved data monitoring capabilities. REpresentational State Transfer (REST) is a software architectural style that describes a uniform interface between physically separate components, often across the Internet in a client-server architecture. []

Next Generation of Data Movement and Processing Platform at Netflix
Netflix engineering recently published in a tech blog how they used data mesh architecture and principles as the next generation of data platform and processing to unleash more business use cases and opportunities. Data mesh is the new paradigm shift in data management that enables users to easily import and use data without transporting it to a centralized location like a data lake. []

Design Patterns and Principles That Support Large Scale Systems
Today even small startups may have to work with terabytes of data or build services that support hundreds of thousands of events per minute (or even a second!). By "scale", we usually refer to a large amount of requests/data/events that the system should handle in a short time period. by Nir Alfasi []
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:
Follow on Twitter    Forward to Friend    Subscribe
Copyright © 2022 LaunchAny, All rights reserved.
unsubscribe from this list