DevSpace (for Kubernetes and Docker) VS Spot.io

DevSpace is very similar to Skaffold in terms of features, with the added benefits of a dedicated UI and a two-way file sync. The UI gives your team an overview of the stack and easy access to logs. At the same time, the file synchronization feature makes their development process faster by letting them directly change code from a running container. - Source: dev.to / almost 2 years ago

DevSpace is an open-source developer tool for Kubernetes that lets you develop and deploy cloud-native software faster. It is a client-only CLI tool that runs on your machine and works with any Kubernetes cluster. You can use it to automate image building and deployments, to develop software directly inside Kubernetes and to streamline workflows across your team as well as across dev, staging and production. - Source: dev.to / about 2 years ago

And speaking of cycle times, the Loft team has also built DevSpace, a developer workflow tool for engineers working with Kubernetes clusters. Have you ever waited around for a new container to build so you can see if your changes work? Or even worse, for a CI pipeline to run integration tests? With DevSpace you can hot reload your app in the running container as you make changes. It's super cool and it's open... - Source: dev.to / about 3 years ago

+1 In my previous stint, I had worked with Spot (https://spot.io/) as one of our vendors. Absolutely great product, amazing customer support and ability to take feature requests, or otherwise address our pain points quickly and effectively. - Source: Hacker News / 10 days ago

FWIW, I am also a big spot.io fan for our workload. During the holidays I run 30-50% spot instances and run 100% spot most of the year. Source: over 1 year ago

Also, you definitely should look into Reservations, and (sale pitch coming) Spot can help you manage those. Source: over 1 year ago

All of this is on spot-instances. We used spot.io (I believe the product is called "Ocean") and they basically took care of all the backend logic to make spot-instances available for the ECS cluster. Source: about 2 years ago

Does cloud provider matter? I would say/think so. Not just cloud provider, but further more, how you set it up, which begets cloud provider. Are you setting it up with only the aws cli? Or did you terraform it? Maybe you chose a particular terraform module or maybe you used eksctl. Maybe you used kops or kubeadm. All these things matter when you get to cluster autoscaling, tainting particular node types to... Source: almost 3 years ago