{"id":102410,"date":"2021-11-28T09:36:38","date_gmt":"2021-11-28T07:36:39","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-postgrest-9-0-0-nadstrojki-dlya-prevrashheniya-bd-v-api-restful"},"modified":"2021-11-28T09:36:38","modified_gmt":"2021-11-28T07:36:39","slug":"reliz-postgrest-9-0-0-nadstrojki-dlya-prevrashheniya-bd-v-api-restful","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-postgrest-9-0-0-nadstrojki-dlya-prevrashheniya-bd-v-api-restful","title":{"rendered":"PostgREST 9.0.0 Release: A Layer to Turn Databases into RESTful APIs","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

The release of PostgREST 9.0.0 has taken place, featuring a standalone web server that implements a lightweight layer for PostgreSQL databases, translating objects from an existing database into a RESTful API. Instead of reflecting relational data into objects (ORM), PostgREST views are created directly in the database. JSON response serialization, data validation, and authorization are also performed on the database side. The system's performance is sufficient to handle up to 2000 requests per second under typical loads. server<\/a>The project code is written in Haskell and is distributed under the MIT license. <\/p>\n

For example, by using only the privilege mechanism in the database, access to data (tables, views, and stored procedures) can be provided via HTTP protocol. There is no need to encode such translation, and usually a single GRANT command is sufficient to make the table available via REST API. It is possible to configure access via tokens (JWT) and organize \"multitenancy\" through the use of dynamic row-level security. <\/p>\n

Architecturally, PostgREST encourages a Data-Oriented Architecture, where microservices do not maintain their state but use a single point of access to the data (Data Access Layer).

\"PostgREST<\/center> <\/p>\n

Among the changes in the new version: <\/p>\n