SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished 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 PostgreSQL, from before an official adapter existed.

Facts

Last push

Where it sits

Lives in
Demonstrates
Database connectorsCAPDatabase connectorscapabilityConnecting 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
PostgreSQLPostgreSQLoutside the atlasNamed as a dependency in its documentation.

Who is behind it

Gregor WolfGregor WolfPersonMaintains this
In the atlas: maintains 17, contributes to 59, wrote 2
@gregorwolf
maintainerSteven De Saeger ( Sedacrivity )PersonContributes to this
In the atlas: contributes to 1
@sedacrivity
1 contributor

What it declares

Every artifact

Type
Sample
Origin
Independently maintained

As a sample

Form
does not say

Connections3

ArchitectureBetaRead from the sample's deployment descriptor. Some of the connections it states are not drawn yet.

as mta.yaml states it at 3e1998f, read
SAP BTP, Cloud Foundry Runtimepg-beershopmta.yaml, module pg-beershop-app, requires pg-beershop-destination-servicebinding, outboundmta.yaml, module pg-beershop-app, requires srv-apisrv-apiSAP Destination service, destination, liteSAP Destinationservicepg-beershop-srv, nodejspg-beershop-srvpg-beershop-app, nodejspg-beershop-apppg-beershop-db-deployer, nodejspg-beershop-db-deplo…pg-beershop-adminer, applicationpg-beershop-adminerpg-beershop-uaa, service instancepg-beershop-uaaPostgreSQL on SAP BTP, hyperscaler option, postgresql-db, trialPostgreSQL on SAPBTP, hyperscaleroption
SAPnot SAP's, or the project's ownstated in the document

Bound, and not drawn

Documented, with no instance in the document

README

quoted from gregorwolf/pg-beershop, read
gregorwolf/pg-beershop/README.mdOn GitHub

CAP Beershop using PostgreSQL for persistence

Build Status

excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered here, gregorwolfchecked
github.com/gregorwolf/pg-beershoptree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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
Contributors1

From the repository’s contributor list, .

History in the atlas2
  1. 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.
  2. First seen.
For your agent
Ref
artifact:gregorwolf-pg-beershop
JSON
/artifacts/gregorwolf-pg-beershop.json
MCP
Connecting an agent