Person
mariayord
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).GraphQLCAPGraphQLServing the same model over GraphQL instead of OData — one endpoint, the client naming the fields it wants, for consumers who expect that shape rather than an OData one.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.TypingCAPTypingMaking the model visible to the compiler — generated types for entities and events so a rename breaks the build rather than production.
Entries
Group by10 of 10 entries
EntrySignals
Contributes to
@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-types@cap-js/cds-typesType definitions for the CAP Node.js SDK.sap official, cap
Type definitions for the CAP Node.js SDK
@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/graphql@cap-js/graphqlA protocol adapter that generates a GraphQL schema from the model and serves it, so the same services answer GraphQL without a second definition of them.sap official, cap
GraphQL protocol adapter generated from the CDS model
@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
Details
For your agent
- Ref
actor:mariayord- JSON
- /actors/mariayord.json
- MCP
- Connecting an agent