3 ms·
Can someone clarify if they mean development environments, or if they're talking about a service that they sell that's related to development environments. Bec
by preommr 2y ago
Can someone clarify if they mean development environments, or if they're talking about a service that they sell that's related to development environments.
Because I don't understand most of the article if it's the former. How are things like performance are a concern for internal development environments? And why are so many things stateful - ideally there should be some kind of configuration/secret management solution so that deployments are consistent.
If it's the latter, then this is incredibly niche and maybe interesting, but unlikely to be applicable to anyone else.
- wutwutwat 2y ago4th paragraph in if you read the article… > This is not a story of whether or not to use Kubernetes for production workloads that’s a whole separate conversation. As is the topic of how to build a comprehensive soup-to-nuts developer experience for shipping applications on Kubernetes. > This is the story of how (not) to build development environments in the cloud.
- epgui 2y agoI'm not sure that this really answers their question.
- wutwutwat 2y ago> Can someone clarify if they mean development environments, or if they're talking about a service that they sell that's related to development environments. their question isn't asking anything. It's both about development environments AND a service they sell, which is dev envs. Even so > This is the story of how (not) to build development environments in the cloud. that is what the article is about. Their words. The person asked what the article is about, this it it, from the authors themselves. read the damn article
- bittermandel 2y agoIt's for running their commercial products, which are stateful and long-lived developer environments.