This is what I have in my mind as base features:

• drawing diagrams using our light weight diagram lib

• save the diagram as yaml or json

• using diagram as input, generate code for Rest APIs & microservices (authentication, authorization, CRUD, data types/objects, etc.). Basically build the features what are there in amplication tool but for microservices + event-driven + progressive apps architectures

• convert env variables to K8s resources (configmaps, secrets, etc.)

• generate K8s manifest files for the microservice application created using Kustomize

• push code to any git repo (automated cli)

• sign the image using cosign (automated cli)

• build container image & push to any container registry (automated cli)

• add auto instrumentation mechanisms for different programming languages to use openTelemetry for distributed tracing using openTelemetry Controller

• ssl/tls support of the app via cert-manager

• API gateway configs creation (Kong, Tyk, Linkerd, Istio)

• vulnerability scan & report generation

• sbom report generation

• services catalog with versioning

• there should not be dependency on any DB, every Compage generated configs, metadata, etc. should be saved into git as yaml/json

• built-in vscode (this is least priority for phase1)

• for phase1 no need to compile Compage into webassembly. full tool should be containerized and should be able to run locally on local K8s or docker.

Mahendra - Do you think I missed anything from a developer perspective which usually developer does as hands-on? Please add which would be vital for phase 1.