←back to thread

Tilt: dev environment as code

(github.com)
136 points saikatsg | 1 comments | 26 Apr 25 19:14 UTC | HN request time: 0.211s | source
Show context
siliconc0w ◴[26 Apr 25 21:37 UTC] No.43807429[source]▶
You're always trading off speed with fidelity. Usually, trying to maintain a local integration environment is going to become too slow and expensive. The problem isn't even necessarily Kubernetes, but as dependencies increase it just gets slower and slower to try and run a copy of the world locally.

I like a fast svelte dev environment with something like docker-compose which might require some mocked out dependencies to keep things fast and then using Kubernetes for other environments once I have local tests passing.

replies(2): >>43807630 #>>43816909 #
1. cirego ◴[26 Apr 25 22:07 UTC] No.43807630[source]▶
I think that's a fair point -- you're making a tradeoff. And the best part is that you don't need to choose one or the other.

In my case, I find that I prefer having higher fidelity and simpler service code by using Tilt to avoid mocks. It's also nice for frontend development because, using a Kubernetes ingress, you can avoid the need for things like frontend proxies, CORS and other development-only setup.