onedevatlasBeta
Browse the atlas
Person

Johannes Vogel

25contributes to
GitHub@johannes-vogel

Capabilities13

Contributes to 13
Agent toolingCAPBTPAgent toolingcapabilityBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.AttachmentsCAPBTPAttachmentscapabilityStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.Audit loggingCAPBTPAudit loggingcapabilityRecording 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.Change trackingCAPChange trackingcapabilityKeeping a readable history of what changed on a record, who changed it and when — as business history rather than database journalling.Database connectorsCAPBTPDatabase 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).Event MeshCAPBTPEvent MeshcapabilityEmitting 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).Feature togglesCAPBTPFeature togglescapabilityTurning behaviour on and off per tenant or per user at runtime, without redeploying, and knowing which toggles are live. System-level switches for delivered objects and runtime flags for unfinished features share the name.GraphQLCAPGraphQLcapabilityServing 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.LoggingCAPBTPLoggingcapabilitySeeing 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.ODataCAPODatacapabilityExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.Serve your application over MCPCAPBTPServe your application over MCPcapabilityExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).TestingCAPBTPTestingcapabilityProving 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.TypingCAPTypingcapabilityMaking the model visible to the compiler — generated types for entities and events so a rename breaks the build rather than production.

Entries25

Group by25 of 25 entries
EntrySignals
Contributes to25
@cap-js-community/feature-toggle-libraryv1.3.6
none

Live-updatable feature toggles for CAP, backed by Redis

@cap-js-community/odata-v2-adapterv1.16.2
none

Exposes a CAP service as OData V2

@cap-js/agentsv0.9.9
Functional boundary

CDS plugin for building agents inside a CAP service

@cap-js/attachmentsv4.0.0
none

CAP Node.js attachments with database, S3, Azure or GCP storage

@cap-js/audit-loggingv1.3.0
none

CAP integration with the SAP Audit Log service

@cap-js/cds-dbsv1.3.1
none

Monorepo of CAP's SQL database services

@cap-js/cds-testv1.0.2
none

Test support for CAP Node.js: server start, HTTP client, assertions

@cap-js/cds-typerv0.41.1
none

Generates TypeScript types from a CDS model

@cap-js/cds-typesv0.20.0
none

Type definitions for the CAP Node.js SDK

@cap-js/change-trackingv2.2.3
none

Change history for annotated CAP entities

@cap-js/db-servicev3.1.2
none

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

@cap-js/event-brokerv0.3.1
none

Consumes events from SAP Cloud Application Event Hub in CAP

@cap-js/graphqlv0.14.0
none

GraphQL protocol adapter generated from the CDS model

@cap-js/hanav3.1.2
none

SAP HANA database service for CAP

@cap-js/mcpv1.5.0
Functional boundary

Exposes CAP services as MCP servers for AI agents

@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/bookshop
none

CAP's getting-started bookshop sample

capire/bookstore
none

Composite CAP app from separately deployed services

capire/docs
none

Sources of capire, the CAP documentation

capire/incidents-app
none

Incident Management reference application for CAP

hdbv2.30.1
Functional boundary

Pure JavaScript SAP HANA driver for Node.js

SAP-samples/cap-sflight
none

Travel-booking reference app on CAP Node.js and Java backends

SAP-samples/fiori-elements-v4-cap-advanced
none

Exercise solutions for the UX405 course on Fiori elements with CAP

xtravels
none

CAP travel-booking app built on xflights master data

Details

For your agent
Ref
actor:johannes-vogel
JSON
/actors/johannes-vogel.json
MCP
Connecting an agent