Outside the atlasOutside the atlastypeA thing outside the atlas that something inside it depends on or talks to. It is named here so that the dependency or the connection can be an edge; it is not rated, not covered and never an artifact.See every one →

PostgreSQL

A relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL.

Open postgresql.orgchecked

Where it sits

Kind
Software

Used by10

@cap-js/postgresby SAPpart of @cap-js/cds-dbs

Dependency relationship.

@cds-pgroll/postgresindependently maintained

Dependency relationship.

Optionally used: a high availability setup; the requirement is marked Optional; Required for HA the database an Edge Integration Cell uses at version 15, with password authentication and at least 1 CPU and 2 GiB

cap-postgres-btp-connectivityindependently maintained

Dependency relationship.

cds-cachingindependently maintained

Optionally used: When store: "postgres" is selected. Cache storage through @keyv/postgres; other store modes do not require this backend.

Functional boundary

When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.

cds-pgindependently maintained

Dependency relationship.

RepositoryThe declared repository is archived
GitHub reports the repository as archived. The package may remain installable, but its source is no longer open for normal maintenance.observed

Dependency relationship.

open-abap-lockby a community org

Required dependency. the database backend its locks are taken in, used only on the DEFAULT connection

LicenceNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.observed
open-steamgateindependently maintained

Optionally used: the PostgreSQL backend is chosen the database behind the eleven-method seam when PostgreSQL is chosen; a release carries a postgres.yml compose file that starts one

Functional boundary

Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.

pg-beershopindependently maintained

Dependency relationship.

Connected from2

cap-postgres-btp-connectivityindependently maintained

data, SOCKS5, TCP, outbound. Opening the database connection of a CAP application to a PostgreSQL server in a private network, through the Connectivity service's SOCKS5 endpoint and a TCP mapping in the Cloud Connector.

data. keeps application and operational data, isolated per tenant by schema

On BTP1

A managed PostgreSQL from the underlying hyperscaler — AWS, Azure, Google Cloud or Alicloud — consumed through a BTP service binding.

Details

Graph13
← POINTS HERE
POINTS OUT →
nothing yet
For your agent