This page describes the architecture of PostgREST.
This section talks briefly about various important modules.
The starting points of the program are:
App.hs
is then in charge of composing the different modules.
Auth.hs is in charge of authn
.
ApiRequest.hs is in charge of parsing the URL query string (following PostgREST syntax), the request headers, and the request body.
A request might be rejected at this level if it's invalid. For example when providing an unknown media type to PostgREST or using an unknown HTTP method.
Using the Schema Cache, Plan.hs fills in out-of-band SQL details (like an ON CONFLICT (pk)
clause) required to complete the user request.
A request might be rejected at this level if it's invalid. For example when doing resource embedding on a nonexistent resource.
Query.hs generates the SQL queries (parametrized and prepared) required to satisfy the user request.
Only at this stage a connection from the pool might be used.
SchemaCache.hs is in charge of schema_cache
.
Config.hs is in charge of configuration
.
Admin.hs is in charge of the admin_server
.