Person

Lothar Bender

Capabilities4

Contributes to 4
Async processingCAPAsync processingcapabilityDoing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.Database connectorsCAPDatabase connectorscapabilityConnecting 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).Job schedulingCAPJob schedulingcapabilityRunning something later, or on a cadence, without keeping a process alive to do it — a nightly job, a retry in an hour, a report on the first of the month — and knowing afterwards whether it ran.Schema evolutionCAPSchema evolutioncapabilityGetting a model change into a database that already holds data, in every tenant, without losing any of it. Generating the initial schema and migrating one that already holds data are often treated as the same step.

Entries9

Group by9 of 9 entries
EntrySignals
Contributes to9
@cap-js-community/event-queuev2.3.2
Functional boundary

Transactional processing of asynchronous and periodic CAP events

@cap-js/cds-dbsv1.3.1
none

Monorepo of CAP's SQL database services

@cap-js/db-servicev3.1.2
none

Base service shared by CAP's SQLite, PostgreSQL and HANA services

@cap-js/hanav3.1.2
none

SAP HANA database service for CAP

@cap-js/postgresv3.1.2
none

PostgreSQL database service for CAP

@cap-js/sqlitev3.1.2
none

SQLite database service for CAP, in memory during development

capire/docs
none

Sources of capire, the CAP documentation

cds-dbmv0.1.4
Archived+1

Delta deployment and migrations for CAP database adapters

SAP-samples/cloud-cap-samples-java
none

Bookshop app demonstrating the CAP Java SDK end to end

Details

For your agent