> I think nobody really talks about this, but unless you have a docker-compose.yml that includes everything you need for local development (...) Is this a prob

> I think nobody really talks about this, but unless you have a docker-compose.yml that includes everything you need for local development (...) Is this a problem? I mean, in this scenario docker compose serves two main purposes: launch a few mock services, and configure those services according to your needs. This means configuring them to consume services already deployed to a cloud environment of your choice. This is something you control. Then all that's left is the service (or set if services) you need to modify. You run those locally and configure them to consume a mix of the mocked services and the services deployed to a cloud environment. > (...) it's increasingly more likely that you'll end up coupling things to Kubernetes to such a degree that running without it (and its abstractions) will become more effort than a person can muster. That coupling can only happen if you intentionally add it yourself. If you need to run your services in isolation, you will be more mindful of the need to not introduce that sort of coupling.