Get the latest tech news

The API database architecture – Stop writing HTTP-GET endpoints


The API database architecture - Stop writing HTTP-GET endpoints

Essential for the architecture is the conceptual split between data retrieval via HTTP GET and data-modifying requests which use the HTTP-verbs POST, PUT, PATCH, DELETE, or a different, non-HTTP mechanism. Data modification can be modeled using PostgREST by exposing stored procedures as POST endpoints, but I recommend using that capability only sparingly and instead developing business logic traditionally in the backend. While the API database architecture supports combining and aggregating resources in an equally or more flexible way, the data modification side of GraphQL cannot be easily replaced.

Get the Android app

Or read this on Hacker News

Read more on:

Photo of API

API

Photo of Endpoints

Endpoints

Related news:

News photo

EQT snaps up API and identity management software company WSO2 for more than $600M

News photo

Delimited Generators – A more natural API for JS generators

News photo

Chilean instant payments API startup Fintoc raises $7 million to turn Mexico into its main market