11 lines
1.4 KiB
Markdown
11 lines
1.4 KiB
Markdown
|
|
||
|
|
## 2026-03-01: Camel Ops Startup - Architecture & Strategy
|
||
|
|
- **Market Focus:** DACH (requires local data persistence/Zero-Trust Payload due to BaFin/compliance) and BENELUX (logistics/EDI tracking).
|
||
|
|
- **Architecture:** Hybrid SaaS. The Control Plane lives in the cloud for management, but the execution Runner and persistence layer (VictoriaMetrics/VictoriaLogs) reside entirely on the customer's infrastructure.
|
||
|
|
- **Deployment Philosophy:** Must offer a frictionless "Black Box" install (`curl | bash` to an empty Alpine VM using embedded k3s) for ops-less teams, alongside a native Helm chart for enterprise K8s teams.
|
||
|
|
- **Tech Stack:** React (modern UX, Cmd+K, visual flows, slide-outs) + Java/Quarkus (SaaS backend and customer runners).
|
||
|
|
- **Key Requirements:** Concise tech stack (few vendors), full-text search, horizontal scaling, no important OSS features behind a paywall.
|
||
|
|
- **Product Strategy:** "Build in public" but retain closed-source core. Modernize the old nJAMS UX paradigm.
|
||
|
|
- **Hendrik's Directives:** Will accept a single-node converged appliance for the 6-week MVP to ensure speed, but **HA/LB and multi-node (Hub/Worker split) are hard requirements for medium-term enterprise sign-offs**. The architecture must support this from Day 1.
|
||
|
|
- **Working Style:** Prefers delegating to specialized AI agents (PM, Architect, Dev) and expects them to critically analyze trade-offs rather than executing blindly.
|