#api-design

[ follow ]
#graphql

How to get started with GraphQL

GraphQL is an open standard for creating web-based APIs that use formal schemas and type systems for consistency.

Understanding the Twitter API So You Can Design Your Own | HackerNoon

The article delves into the design considerations of the X home timeline API, highlighting how it addresses complex data fetching and interactions.

GraphQL root fields

Root fields in GraphQL are not special; all types have fields, leading to misconceptions and design choices.

How to get started with GraphQL

GraphQL is an open standard for creating web-based APIs that use formal schemas and type systems for consistency.

Understanding the Twitter API So You Can Design Your Own | HackerNoon

The article delves into the design considerations of the X home timeline API, highlighting how it addresses complex data fetching and interactions.

GraphQL root fields

Root fields in GraphQL are not special; all types have fields, leading to misconceptions and design choices.
moregraphql

API Design: GraphQL vs. REST, Contract Maintenance, and Integration Strategies - JSJ 661 - JavaScript Jabber

API design, logging best practices, and configuration management are crucial for developers to optimize large-scale ecosystems.
#http-methods

API with NestJS #175. PUT and PATCH requests with PostgreSQL and Drizzle ORM

Understanding the differences between PUT and PATCH methods is crucial for effective API design and data manipulation.

Understanding PUT vs PATCH: Key Differences and Use Cases

PUT replaces an entire resource, while PATCH updates only specified fields, making PATCH more efficient for targeted changes.

API with NestJS #175. PUT and PATCH requests with PostgreSQL and Drizzle ORM

Understanding the differences between PUT and PATCH methods is crucial for effective API design and data manipulation.

Understanding PUT vs PATCH: Key Differences and Use Cases

PUT replaces an entire resource, while PATCH updates only specified fields, making PATCH more efficient for targeted changes.
morehttp-methods

Designing the APIs that accidentally power businesses

Developer-driven design must balance user experience and development velocity.
The ideal API design for users is general functions for simplicity.
Specific functions enhance optimization but complicate user consumption.

Don't return named tuples in new APIs

Named tuples should be used when tuple return types become insufficiently descriptive due to API expansion.
Starting with named tuples complicates API usage due to dual access methods for users.

Your Architecture Cheat Sheet to API Design Styles | HackerNoon

Understanding various API design approaches is essential for building reliable APIs that meet specific business needs.

Improving No-Code APIs with PostgreSQL, PostgREST, and Apache APISIX | HackerNoon

PostgREST SELECT mechanism offers powerful query capabilities but can be complex, while Apache APISIX can simplify API design by rewriting and forwarding requests.

Why Patching Globals Is Harmful

Patching globals in code can have significant impacts, often leading to misunderstandings and disagreements among developers.

What Are the Core Principles of Good API Design?

An API should be easy to learn and write to, and hard to misuse.
A good design takes into account the evolution of an API.

Developer Experience Book

Streamline core workflows for maximum velocity
Design self-explanatory APIs and create useful documentation
[ Load more ]