PackagePackagetypeA library you install and call yourself.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
@cap-js/cds-dbs
The monorepo behind CAP's SQL database services — the base service, SQLite, PostgreSQLPostgreSQLoutside the atlasA 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. and HANA all live here, which is why they version together.
A monorepo, not a package: nothing installs from its root. Four modules live in it — @cap-js/db-service@cap-js/db-servicepackageThe base every CAP database service is built on: the shared query translation and pooling that SQLite, PostgreSQL and HANA specialise rather than reimplement.sap official, cap, the base, and @cap-js/sqlite@cap-js/sqlitecds-pluginThe SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.sap official, cap, @cap-js/postgres@cap-js/postgrescds-pluginThe PostgreSQL database service — the production option for running CAP off HANA, sharing the base service with the other three.sap official, cap and @cap-js/hana@cap-js/hanacds-pluginThe HANA database service — the production default, on the same streamlined architecture as the SQLite and PostgreSQL services.sap official, cap, which implement that interface for their own database — each in its own subfolder with its own README, each published to npm on its own. A project adds one of those packages; the repository is where their issues are filed and where the shared code sits.
SAP Cloud Application Programming ModelSAP Cloud Application Programming ModelOrganisationMaintains this In the atlas: maintains 34@cap-jsmaintainerJohannes VogtPersonContributes to this In the atlas: maintains 1, contributes to 28, wrote 10@AkatuoroArley Triana MorinPersonContributes to this In the atlas: contributes to 9, wrote 1@arleytmAndreas SchmidtPersonContributes to this In the atlas: contributes to 6@aschmidt93Bob den OsPersonContributes to this In the atlas: contributes to 13@BobdenOsAndre MeyeringPersonContributes to this In the atlas: contributes to 10@bugwelleCAP BotPersonContributes to this In the atlas: contributes to 5@cap-botsChristian GeorgiPersonContributes to this In the atlas: maintains 1, contributes to 53@chgeoChristian SchüringsPersonContributes to this In the atlas: contributes to 25@cschueringsDaniel HutzelPersonContributes to this In the atlas: contributes to 32, wrote 3@danjoaDaniel O'GradyPersonContributes to this In the atlas: contributes to 10@daogrady35 contributors
What it declares
Every artifact
Type
Package
Origin
By SAP
As a package
Where it runs
does not say
declared, Where the library runs once installed: inside its host (loaded into the CAP application, installed into the ABAP system, loaded by the UI5 application), in a program of your own, or only at build time.
Distributed through
npm
declared, How it is installed, as its documentation tells a user to get it., read npm add @cap-js/sqlite -D — @cap-js/cds-dbs — README, 2026-10-18
Parts and add-ons4
Parts 4
CDS plugins3
@cap-js/hanaby SAPThe HANA database service — the production default, on the same streamlined architecture as the SQLite@cap-js/sqlitecds-pluginThe SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.sap official, cap and PostgreSQL@cap-js/postgrescds-pluginThe PostgreSQL database service — the production option for running CAP off HANA, sharing the base service with the other three.sap official, cap services.
@cap-js/postgresby SAPThe PostgreSQLPostgreSQLoutside the atlasA 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. database service — the production option for running CAP off HANA, sharing the base service with the other three.
@cap-js/sqliteby SAPThe SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.
Packages1
@cap-js/db-serviceby SAPThe base every CAP database service is built on: the shared query translation and pooling that SQLite, PostgreSQLPostgreSQLoutside the atlasA 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. and HANA specialise rather than reimplement.
Connections5
Group by
NodeRelationConditionBasis
Functional1
Database connectorsDatabase connectorscapabilityConnecting a data model and its queries to a databaseSAP and community, narrow by design
→provides through a part
through @cap-js/db-service, @cap-js/hana, @cap-js/postgres, @cap-js/sqlite
provides through a part Database connectors
Functional, derived, through @cap-js/db-service, @cap-js/hana, @cap-js/postgres, @cap-js/sqlite
derived
provides through a part Database connectors
Functional, derived, through @cap-js/db-service, @cap-js/hana, @cap-js/postgres, @cap-js/sqlite
Connecting a data model and its queries to a database
Lineage4
@cap-js/db-service@cap-js/db-servicepackageBase service shared by CAP's SQLite, PostgreSQL and HANA servicessap official, cap
←has part
through inverted from its part_of edge
has part @cap-js/db-service
Lineage, derived, through inverted from its part_of edge
derived
has part @cap-js/db-service
Lineage, derived, through inverted from its part_of edge
Base service shared by CAP's SQLite, PostgreSQL and HANA services
@cap-js/hana@cap-js/hanacds-pluginSAP HANA database service for CAPsap official, cap
←has part
through inverted from its part_of edge
has part @cap-js/hana
Lineage, derived, through inverted from its part_of edge
derived
has part @cap-js/hana
Lineage, derived, through inverted from its part_of edge
SAP HANA database service for CAP
@cap-js/postgres@cap-js/postgrescds-pluginPostgreSQL database service for CAPsap official, cap
←has part
through inverted from its part_of edge
has part @cap-js/postgres
Lineage, derived, through inverted from its part_of edge
derived
has part @cap-js/postgres
Lineage, derived, through inverted from its part_of edge
PostgreSQL database service for CAP
@cap-js/sqlite@cap-js/sqlitecds-pluginSQLite database service for CAP, in memory during developmentsap official, cap
←has part
through inverted from its part_of edge
has part @cap-js/sqlite
Lineage, derived, through inverted from its part_of edge
derived
has part @cap-js/sqlite
Lineage, derived, through inverted from its part_of edge
SQLite database service for CAP, in memory during development
This project is open to feature requests/suggestions, bug reports etc. via GitHub issues.
Contribution
Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.
Code of Conduct
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.
Licensing
Copyright 2024 SAP SE or an SAP affiliate company and cds-dbs contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.
The repository's README titles itself 'Welcome to the @cap-js/cds-dbs Monorepo', and that scope is not on npm — a request for @cap-js/cds-dbs returns 404. The bare name is taken: npm's cds-dbs is one release, 1.3.1 of 2024-12-10, published by cosmo83 (arava@sat-infotech.com) with the description 'This is a monorepo for our SQL Database Services.' copied from this README. Because the crawler resolves a package by the entry's name, that stranger's record is what data/crawled/health.json carries for this artifact today: latest_version 1.3.1, one release, four weekly downloads, one maintainer and a 'SEE LICENSE' licence, beside GitHub facts read from cap-js/cds-dbs. The repository's own name ends the mis-join.
The monorepo is not an option anyone adds to a project. Its README states what is: 'Each of the subfolders is published as individual npm module', and 'In general, all you need to do is to install one of the database packages, as follows:'. The four packages carry the capability edge; the repository listed beside them made five options out of four. It stays a node — the four now point up at it with part_of.
A monorepo, not a package: nothing installs from its root. Four modules live in it — @cap-js/db-service, the base, and @cap-js/sqlite, @cap-js/postgres and @cap-js/hana, which implement that interface for their own database — each in its own subfolder with its own README, each published to npm on its own. A project adds one of those packages; the repository is where their issues are filed and where the shared code sits.
Typed cds-plugin by placement, which defaults every candidate to that. It is not one.
The monorepo behind CAP's SQL database services — the base service, SQLite, PostgreSQL and HANA all live here, which is why they version together.
