TypeScript patterns

How a CAP service is arranged once it is written in TypeScript — where handlers live, what registers them, and how business logic is kept apart from persistence. Distinct from typing, which is about the model being visible to the compiler; this is about the shape of the code around it.

Showing artifacts, examples and content with confirmed Java applicability. View All CAP

Overview

DOES NOT APPLY IN JAVA

The CAP Java SDK develops CAP applications in Java, with Java 21 as its minimum, so a service's custom logic in this flavor is Java code and there is no TypeScript in srv to arrange. Not applicable rather than unmapped: the concern does not exist here, which is not the same as nobody having built for it.

SourceGetting Started — CAP Javachecked 2026-10-15

Artifacts

Nothing is mapped here yet.

Details

Coverage

statenot applicable, CAP, Java

assessed2026-10-15

domainDeveloper Experience

SourceGetting Started — CAP Javachecked 2026-10-15SourceGetting Started — CAP Java, the Java versionchecked 2026-10-15SourceTypeScript — capire, a Node.js pagechecked 2026-10-15

Comparison properties4

These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.

How handlers bindLayers it namesDependency injectionDraft events

For your agent

Ref: capability:typescript-patterns
JSON: /capabilities/typescript-patterns.json
MCP: Connecting an agent