Hacker News with Generative AI: API Design

Stop using REST for state synchronization (2024) (mbid.me)
Most apps need state synchronization, not state transfer. We should replace REST and friends with proper state synchronization protocols where appropriate.

API Design, State Management, Web Development

58 points by Kerrick 8 days ago | 29 comments

Ensure public interface reliability: Tracking API compatibility for Android (revenuecat.com)
Whether you’re building open-source libraries, SDKs, or common modules for other teams, it’s important to make deliberate and careful changes to public APIs, as they directly impact development resources required for migration.

Android Development, Software Development, API Design, Open Source

9 points by skydoves 24 days ago | 1 comments

Event Destinations Initiative: A model for event producer/consumer interop (eventdestinations.org)
A model for event interoperability between event producers and their consumers to favor better developer experience, robust integration, and infrastructural efficiency.

Event Management, Software Development, API Design, Interoperability

10 points by leggetter 85 days ago | 1 comments

API design note: Beware of adding an "Other" enum value (microsoft.com)
Consider the following API:

API Design, Software Development, Programming, Best Practices

236 points by luu 86 days ago | 126 comments

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.

API Design, REST, RPC, gRPC, OpenAPI

323 points by hui-zheng 121 days ago | 276 comments

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.

API Design, Programming, Software Development

72 points by todsacerdoti 202 days ago | 66 comments

Ziggy: Data serialization language for expressing API messages, config files (ziggy-lang.io)

Data Serialization, Programming Languages, API Design, Configuration Files

104 points by thunderbong 229 days ago | 16 comments

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.

Programming, API Design, Customer Support

10 points by kderbyma 239 days ago | 3 comments

Design a GraphQL Schema – how to continuously evolve your schema (tailcall.run)

GraphQL, API Design, Software Development

12 points by amitksingh1490 302 days ago | 2 comments

Malloc() and free() are a bad API (2022) (foonathan.net)

Memory Management, Programming, API Design

49 points by davikr 313 days ago | 26 comments

The API database architecture – Stop writing HTTP-GET endpoints (fabianzeindl.com)

API Design, Databases, Software Architecture

93 points by fzeindl 378 days ago | 164 comments

TypeSpec: A new language for API-centric development (typespec.io)