Hacker News with Generative AI: API Design

Understanding gRPC, OpenAPI and REST and when to use them in API design (2020) (cloud.google.com)
As most software developers no doubt know, there are two primary models for API design: RPC and REST. Regardless of model, most modern APIs are implemented by mapping them in one way or another to the same HTTP protocol. It has also become common for RPC API designs to adopt one or two ideas from HTTP while staying within the RPC model, which has increased the range of choices that an API designer faces.
Don't return named tuples in new APIs (snarky.ca)
In my opinion, you should only introduce a named tuple to your code when you're updating a preexisting API that was already returning a tuple or you are wrapping a tuple return value from another API.
Ziggy: Data serialization language for expressing API messages, config files (ziggy-lang.io)
Amazon APIs are the worst. No comparison. *Rant (ycombinator.com)
Working with amazon API's is single handedly the worst experience I have ever had programming. They are a textbook example of how to build the worst architecture, and their support system is designed to be almost unusable.
Design a GraphQL Schema – how to continuously evolve your schema (tailcall.run)
Malloc() and free() are a bad API (2022) (foonathan.net)
The API database architecture – Stop writing HTTP-GET endpoints (fabianzeindl.com)
TypeSpec: A new language for API-centric development (typespec.io)
No Abstractions: our API design principle (increase.com)
The Design of Everyday APIs (2022) (roguelynn.com)