SampleSampleA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
pg-beershop
CAP beershop running on PostgreSQLPostgreSQLA 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., from before an official adapter existed.
Facts
Last push
Where it sits
Lives in
Demonstrates
Database connectorsCAPDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).
Requires
PostgreSQLPostgreSQLNamed as a dependency in its documentation.
Who is behind it
Gregor WolfGregor WolfMaintains this
In the atlas: maintains 17, contributes to 59, wrote 2@gregorwolfmaintainerSteven De Saeger ( Sedacrivity )Contributes to this
In the atlas: contributes to 1@sedacrivity1 contributor
In the atlas: maintains 17, contributes to 59, wrote 2@gregorwolfmaintainerSteven De Saeger ( Sedacrivity )Contributes to this
In the atlas: contributes to 1@sedacrivity1 contributor
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
As a sample
- Form
- does not say
Connections
Group by
NodeRelationBasis
Functional
Database connectorsDatabase connectorsConnecting a data model and its queries to a databaseSAP and community, narrow by design
demonstrates
authored
demonstrates Database connectors
Connecting a data model and its queries to a database
Technical
PostgreSQL on SAP BTP, hyperscaler optionPostgreSQL on SAP BTP, hyperscaler optionManaged PostgreSQL from the hyperscaler via a BTP service bindingsap official, btp
available via
derived
available via PostgreSQL on SAP BTP, hyperscaler option
Managed PostgreSQL from the hyperscaler via a BTP service binding
needs
authored
needs 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.
Download
Architecture
as mta.yaml states it at 3e1998f, readDownload
SAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp
PostgreSQL on SAP BTP, hyperscaler optionA managed PostgreSQL from the underlying hyperscaler — AWS, Azure, Google Cloud or Alicloud — consumed through a BTP service binding.sap official, btp
pg-beershop-app → SAP Destination serviceStated in the descriptor, data, outboundReading the configuration of the destination a route forwards to, where the router's own environment does not define it.
pg-beershop-app → pg-beershop-srvStated in the descriptor, datamta.yaml, module pg-beershop-app, requires srv-api
SAPnot SAP's, or the project's ownstated in the document
Bound, and not drawn
- pg-beershop-db-deployerPostgreSQL on SAP BTP, hyperscaler option
- pg-beershop-adminerPostgreSQL on SAP BTP, hyperscaler option
- pg-beershop-srvPostgreSQL on SAP BTP, hyperscaler option, pg-beershop-uaa
- pg-beershop-apppg-beershop-uaa
Documented, with no instance in the document
- @cap-js/postgres requires PostgreSQLpg-beershop-srv
- @sap/xssec requires SAP Authorization and Trust Management servicepg-beershop-srv
- @sap/xssec requires Cloud Identity Servicespg-beershop-srv
- @sap/approuter requires SAP Authorization and Trust Management servicepg-beershop-appAuthenticating the user on the routes configured to require it: the router binds to it as the UAA server, or to Cloud Identity Services instead.@sap/approuter 23.0.0 — README, user authentication
The User Account and Authentication (UAA) server is responsible for user authentication.
- @sap/approuter requires Cloud Identity Servicespg-beershop-appAuthenticating the user against Identity Authentication instead of, or alongside, SAP Authorization and Trust Management service. Bound to both, the router picks IAS.@sap/approuter 23.0.0 — README, authenticationType
Bound to both services: prefers ias if both authentication services can be used in the current subaccount, determined via BTP security endpoint (may impact response time)
- @sap/approuter requires SAP Connectivity servicepg-beershop-appForwarding to an on-premise backend: the binding is required once a destination sets its ProxyType to on-premise.@sap/approuter 23.0.0 — README, destination ProxyType
if ProxyType set to `on-premise`, binding to SAP Cloud Platform connectivity service is required.
- @sap/approuter requires SAP HTML5 Application Repository service for SAP BTPpg-beershop-appServing static content from the repository rather than from the router's own folder. Bound, both the files and the xs-app.json routes come from there.@sap/approuter 23.0.0 — README, Integration with HTML5 Application Repository
When the application router interacts with HTML5 Application Repository to serve HTML5 Applications, all static content and routes (xs-app.json) are retrieved from HTML5 Application Repository.
README
quoted from gregorwolf/pg-beershop, readgregorwolf/pg-beershop/README.mdthe maintainer’s wordsOn GitHub
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaGitHub API · gregorwolf
first seen in the atlas
ecosystem and domaincap, data-and-persistence
Contributors
History in the atlas
- A sample's domain recorded what kind of thing it is, which artifact_type already says, so it sat under Learning while the capability it demonstrates sat elsewhere — filtering a domain for a worked example returned nothing. Domain now follows the single capability the sample demonstrates; a sample with no single subject stays in Learning.
- First seen.
For your agent
- Ref
artifact:gregorwolf-pg-beershop- JSON
- /artifacts/gregorwolf-pg-beershop.json
- MCP
- Connecting an agent