SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.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 →Reference

shared-db

A CAP sample showing how one domain model is shared across several apps that all rely on it, used to deploy microservices against a shared database, with capire's Microservices with CAP guide as background.

Shows how a model can be shared across multiple apps that all rely on the same domain model; the repository's own description on GitHub is that it is used to deploy micro services with shared DB. SAP states what the sample is for: demonstrating how to create a CAP plugin and how to use it in your application. For the general idea and background the README points at capire's Microservices with CAP guide rather than setting the pattern out here.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Demonstrates
DeploymentCAPDeploymentcapabilityGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.Plugin authoringCAPPlugin authoringcapabilityWriting a package that extends a framework or runtime rather than an application that uses it — a reusable extension loaded by its host, and the question you arrive at once solving a problem twice makes you want to solve it once for everyone.

Who is behind it

Capire Docs & SamplesCapire Docs & SamplesOrganisationMaintains this
In the atlas: maintains 20, wrote 1
@capire
maintainerJohannes VogtPersonContributes to this
In the atlas: maintains 1, contributes to 28, wrote 10
@Akatuoro
Christian GeorgiPersonContributes to this
In the atlas: maintains 1, contributes to 53
@chgeo
Daniel HutzelPersonContributes to this
In the atlas: contributes to 32, wrote 3
@danjoa
René JeglinskyPersonContributes to this
In the atlas: contributes to 20
@renejeglinsky
Steffen WaldmannPersonContributes to this
In the atlas: contributes to 25
@swaldmann
Vladislav LeonkevPersonContributes to this
In the atlas: contributes to 12, wrote 1
@vl-leon
6 contributors

Before choosing this

Conditions

PracticalFunctional boundary

Not in production. SAP states it is just a sample, not optimised for performance or security.

What it declares

Every artifact

Type
Sample
Origin
By SAP
Use as
A reference

As a sample

Form
does not say

Connections2

README

quoted from capire/shared-db under Apache-2.0, read
capire/shared-db/README.mdOn GitHub

@capire/shared-db

Shows how a model can be shared across multiple apps that all rely on the same domain model. See the Microservices with CAP guide for the general idea and background.

Caution

This is just a sample, not intended for production use. It is meant to demonstrate how to create a CAP plugin and how to use it in your application. It is not optimized for performance or security.

License

Copyright (c) 2024 SAP SE or an SAP affiliate company. All rights reserved. This file is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
github.com/capire/shared-dbtree, 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
releases and cadence0
discovered viaAdded by hand
first seen in the atlas
ecosystem and domaincap, operations-and-runtime
Contributors6
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:capire-shared-db
JSON
/artifacts/capire-shared-db.json
MCP
Connecting an agent