Person
Richard Lindner
Capabilities
Contributes to
Feature togglesCAPFeature togglesTurning 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.MultitenancyCAPMultitenancyServing many tenants from one deployment — onboarding, tenant-isolated data, per-tenant schema deployment and the operational tooling around it. It is decided once, before anything is built, and narrows the artifacts in almost every capability downstream: most sharply in [caching](capability:caching) and anything else holding state in process.ODataCAPODataExposing 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.
Entries
Group by
EntrySignals
Contributes to
@cap-js-community/feature-toggle-library@cap-js-community/feature-toggle-libraryLive-updatable feature toggles for CAP applications, backed by Redis.community org, cap
Live-updatable feature toggles for CAP, backed by Redis
@cap-js-community/mtx-tool@cap-js-community/mtx-toolCLI for operating multitenant CAP applications — inspecting, upgrading and repairing tenants across a landscape.community org, cap
CLI for operating tenants of multitenant CAP applications
@cap-js-community/odata-v2-adapter@cap-js-community/odata-v2-adapterExposes a CAP service as OData V2 for clients that cannot move to V4.community org, cap
Exposes a CAP service as OData V2
Details
For your agent
- Ref
actor:rlindner81- JSON
- /actors/rlindner81.json
- MCP
- Connecting an agent