3 ms·
Look into postgrest instead of graphQL as well and use the database as a flexible middle layer to construct your API on demand. http://postgrest.com/en/v0.4/ h
by cel1ne 10y ago
Look into postgrest instead of graphQL as well and use the database as a flexible middle layer to construct your API on demand.
http://postgrest.com/en/v0.4/ http://postgrest.com/en/v0.4/
- StreamBright 10y agoWe did that, due to a lack or experience with graphQL. We use Postgres as a transactional key-value store (with proper schema though). We implemented the filtering as simple params to the API, not as flexible as graphQL but it is straightforward to implement on the backend side. I am not sure what is the meaning of inconsistent API though.