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 →Reference

cap-java-resilience

A CAP Java service consuming a Business Partner API that a CAP Node.js project in the same repository mocks, with the SAP Cloud SDK caching and resilience it is named for recorded as planned.

Two projects in one repository: business-partner-mock, a CAP Node.js service that provides a mock Business Partner API, and cap-java-resilience, the CAP Java service that consumes it — a remote-consumption loop with no real backend behind it. What the repository is named for is not in it: CLAUDE.md files the caching and resilience from SAP Cloud SDK under what "the plan is to add". That file is the only documentation, and the rest of it is instructions for an agent working in the repository.

Facts

Last push

Where it sits

Lives in
Demonstrates
Service integrationCAPService integrationcapabilityUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from [destinations](capability:destinations), which is how the address and the credentials are found, and from [replication](capability:replication), which is holding the data locally.Local developmentCAPLocal developmentcapabilityRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10
@miyasuta
maintainer

Before choosing this

Signals

LicenceNo licenseNeither 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.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Use as
A reference
Runtime
JavaNode.js

As a sample

Form
does not say

Connections2

cap-java-resilience connectionscap-java-resiliencePROVIDES→ demonstrates2demonstrates authoredLocal developmentdemonstrates authoredService integration

Details

Sources2
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/cap-java-resiliencetree, pushes, contributors, CIchecked

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
runtimesjava, node
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
Flavors2
Java
“THis is a CAP Java project” — CLAUDE.md — cap-java-resiliencechecked
Node.js
“This is a CAP Node.js project” — CLAUDE.md — cap-java-resiliencechecked
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-java-resilience
JSON
/artifacts/miyasuta-cap-java-resilience.json
MCP
Connecting an agent