We’ve Used TDK CLI (Including Private Source) for 2 Years: Here’s Why You Need to Know

说明与用途

经过两年的使用，TDK CLI 减少了本地开发的复杂性，加速了新服务的引入，并保持了 Helm 的生产部署，同时保持了配置债务的平稳。

问题

Local development setup was complex, with many Dockerfiles, Compose entries, Traefik rules, and onboarding documentation, leading to maintenance overhead and onboarding delays.

结果

After two years, TDK CLI eliminated local‑development maintenance, collapsed onboarding, enabled reliable hot reload, and justified its $19/month per developer cost by reducing Compose drift and manual wiring.

工作流

• Run tdk doctor to check environment
• Edit service.json for new service
• Run tdk up <stack> to generate artifacts and start Tilt
• Tilt watches code and live‑updates containers
• Develop locally with hot reload and local *.localhost domains

证据

Two years ago our team was drowning in local setup. Every new service meant another Dockerfile, another entry in a sprawling Compose file, another set of Traefik rules, another paragraph in the onboarding wiki, and another “it works on my machine” ticket.

来源

TDK is simple in concept: one service.json per service becomes a full local Docker + Tilt stack. You run tdk up. Production stays on Helm. Local development does not require Kubernetes.

来源

After two years this still feels natural: tdk up identity brings up only what we need. New services are discovered automatically.

来源

Config debt stayed flat. Adding a service is still one service.json plus a short tdk resource command. The generated files are treated as a contract; we run tdk config verify in CI.

来源

New engineers run tdk doctor, clone an example or our private template, then tdk up. The old multi‑page wiki is gone.

来源

We use the licensed generators, Verdaccio local registry, and a few extra scaffolding features. At roughly $19 per developer per month it was cheaper than the hours spent fighting Compose drift.

来源

Windows developers still need WSL2 Ubuntu for full runtime; native Windows is inspection‑only.

来源