docs: move ARCHITECTURE.md to architecture.rst

This commit is contained in:
steve-chavez
2024-04-10 15:51:08 -05:00
committed by Steve Chavez
parent 4428253efe
commit c9136816a2
4 changed files with 65 additions and 53 deletions
-52
View File
@@ -1,52 +0,0 @@
# Architecture
This document describes the high-level architecture of PostgREST.
## Bird's Eye View
![PostgREST Architecture](docs/_static/arch.png)
On the highest level, PostgREST processes the user HTTP request, if it's accepted it generates a SQL query, executes it, and produces a response.
## Code Map
This section talks briefly about various important modules.
The starting points of the program are `main/Main.hs` -> `src/PostgREST/CLI.hs` -> `src/PostgREST/App.hs`.
`App.hs` is then in charge of composing the different modules.
### Auth
It authenticates the request using JWT.
### ApiRequest
PostgREST operates over two types of resources: database relations (tables or views) and database functions; providing different representations (depending on the media type)
for them.
This module is in charge of representing the operation over an `ApiRequest` type. It parses the URL querystring following PostgREST syntax, the request headers, and the request body
(if possible it avoids parsing the body and sends it directly to the db).
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.
### Plan
Using the Schema Cache, this module fills in SQL details that the user might have not specified (like an `ON CONFLICT (pk)` clause ).
A request might be rejected at this level if it's invalid. For example when doing resource embedding on a nonexistent resource.
### Query
This module generates SQL queries that are parametrized and prepared. Only at this stage a connection from the pool might be used.
A query might fail (and be rollbacked) at this level if it doesn't comply to certain conditions, e.g. by not returning a single row when a ``Accept: application/vnd.pgrst.object``
header is specified.
### SchemaCache
This queries the PostgreSQL system catalogs and caches the results into a SchemaCache type, which then is used by the other modules.
### Admin
Admin server exposed in another port, it provides health checks.
+63
View File
@@ -0,0 +1,63 @@
Architecture
############
This page describes the architecture of PostgREST.
Bird's Eye View
===============
.. image:: ../_static/arch.png
Code Map
========
This section talks briefly about various important modules.
The starting points of the program are:
- `Main.hs <https://github.com/PostgREST/postgrest/blob/main/main/Main.hs>`_
- `CLI.hs <https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/CLI.hs>`_
- `App.hs <https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/App.hs>`_
``App.hs`` is then in charge of composing the different modules.
Auth
----
`Auth.hs <https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/Auth.hs>`_ is in charge of :ref:`authn`.
Api Request
-----------
`ApiRequest.hs <https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/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.
Plan
----
Using the Schema Cache, `Plan.hs <https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/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
-----
`Query.hs <https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/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.
Schema Cache
------------
`SchemaCache.hs <https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/SchemaCache.hs>`_ is in charge of :ref:`schema_cache`.
Config
------
`Config.hs <https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/Config.hs>`_ is in charge of :ref:`configuration`.
Admin
-----
`Admin.hs <https://github.com/PostgREST/postgrest/blob/main/src/PostgREST/Admin.hs>`_ is in charge of the :ref:`admin_server`.
+1 -1
View File
@@ -132,7 +132,7 @@ Technical references for PostgREST's functionality.
references/errors.rst
references/configuration.rst
references/observability.rst
references/health_check.rst
references/*
Explanations
------------
+1
View File
@@ -98,6 +98,7 @@ OpenAPI
openapi
ORM
ov
parametrized
passphrase
PBKDF
PgBouncer