Cloud Application APIs and multi-runtime experiments based on Mecha architecture principles.
Documentation · Java SDK · Runtime
Capa Cloud contains projects at different maturity levels. Repository presence does not imply production support; check each README and recent CI before adopting it.
| Project | Role | Status |
|---|---|---|
| capa-java | Rich-SDK implementation for Java applications | Primary Java SDK |
| capa-java-aws | AWS SPI modules for Capa Java | Adapter modules; capability support varies |
| capa.io | Website and bilingual documentation | Public documentation source |
| Project | Language | Status |
|---|---|---|
| capa | Go | Experimental sidecar/runtime; implemented features and roadmap are documented separately |
| cloud-runtimes-jvm | Java | JVM API contracts plus partial adapter scaffolds |
| cloud-runtimes-golang | Go | Interface definitions; module path remains under reactivegroup for compatibility |
| cloud-runtimes-python | Python | Alpha interface definitions; no bundled runtime adapter |
The following repositories preserve earlier integrations, prototypes, or solution work. Treat them as reference material unless their own README and CI state say otherwise:
Capa's rich-SDK path lets an application program against standard runtime APIs while selecting replaceable SPI implementations for its deployment environment.
Application
↓ standard Cloud Runtime APIs
Capa Java SDK
↓ component and SPI contracts
Cloud or middleware adapter
The experimental capa runtime explores a separate sidecar path. Do not assume identical capability coverage between the Java SDK and Go runtime.
The API repositories define contracts across service invocation, configuration, pub/sub, state, secrets, bindings, telemetry, files, locks, and selected native protocols. Actual support depends on the chosen SDK/runtime and adapter.
- Read the Capa overview.
- For Java applications, follow the capa-java README.
- For the Go sidecar experiment, follow the capa README.
- Report documentation problems in capa.io Issues.
Open issues and pull requests in the repository that owns the affected API, SDK, adapter, runtime, or documentation. Public examples must not include credentials, private endpoints, customer data, or personal identifiers.
Most repositories use the Apache License 2.0; verify the license in the specific repository before reuse.