Person
Paul
Capabilities
Contributes to
Audit loggingCAPAudit loggingRecording who touched personal or sensitive data, in a form an auditor accepts, without hand-writing it in every handler. It is often confused with application logging, which records what the code did rather than who accessed what.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).Event MeshCAPEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).LoggingCAPLoggingSeeing what a running service did, in a form something can read afterwards — levels, a formatter that suits a laptop and one that suits a log service.TelemetryCAPTelemetrySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.TestingCAPTestingProving the service still does what it did — against the model and the handlers, without a deployed system and without a database somebody has to keep clean.
Entries
Group by12 of 12 entries
EntrySignals
Contributes to
@cap-js/advanced-event-mesh@cap-js/advanced-event-meshIntegrates CAP with SAP Integration Suite advanced event mesh.sap official, cap
CAP integration with SAP Integration Suite advanced event mesh
@cap-js/audit-logging@cap-js/audit-loggingIntegration with the SAP Audit Log service, so operations on personal data are recorded in the form an auditor expects without the application writing the entries.sap official, cap
CAP integration with the SAP Audit Log service
@cap-js/cds-dbs@cap-js/cds-dbsThe monorepo behind CAP's SQL database services — the base service, SQLite, PostgreSQL and HANA all live here, which is why they version together.sap official, cap
Monorepo of CAP's SQL database services
@cap-js/cds-test@cap-js/cds-testTest support for CAP Node.js, installed as a dev dependency: it starts the project's server for the test, hands the test an HTTP client bound to it, and carries the assertions.sap official, cap
Test support for CAP Node.js: server start, HTTP client, assertions
@cap-js/db-service@cap-js/db-serviceThe base every CAP database service is built on: the shared query translation and pooling that SQLite, PostgreSQL and HANA specialise rather than reimplement.sap official, cap
Base service shared by CAP's SQLite, PostgreSQL and HANA services
@cap-js/hana@cap-js/hanaThe HANA database service — the production default, on the same streamlined architecture as the SQLite and PostgreSQL services.sap official, cap
SAP HANA database service for CAP
@cap-js/postgres@cap-js/postgresThe PostgreSQL database service — the production option for running CAP off HANA, sharing the base service with the other three.sap official, cap
PostgreSQL database service for CAP
@cap-js/sqlite@cap-js/sqliteThe SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.sap official, cap
SQLite database service for CAP, in memory during development
@cap-js/telemetry@cap-js/telemetryAutomatic OpenTelemetry instrumentation for CAP Node.js services and their database calls, exported as traces and metrics to the console, SAP Cloud Logging, Dynatrace, Jaeger or an OTLP endpoint.sap official, cap
OpenTelemetry instrumentation for CAP services
capire/docscapire/docsThe sources of capire itself, in the repository it is built from: the documentation every core_coverage claim in this graph is checked against, so a claim can be dated against a commit.sap official, cap
Sources of capire, the CAP documentation
SAP-samples/cap-sflightSAP-samples/cap-sflightA travel-booking reference application built with CAP and SAP Fiori elements, whose same UIs run against a Node.js and a Java backend so the two stacks can be compared directly.sap official, cap
Travel-booking reference app on CAP Node.js and Java backends
xtravelsxtravelsA travel-booking application built on the master data that xflights publishes, composing another package's schema into its own rather than owning master data itself.sap official, cap
CAP travel-booking app built on xflights master data
Details
For your agent
- Ref
actor:pdt42- JSON
- /actors/pdt42.json
- MCP
- Connecting an agent