31–40 of 40 posts
What is your product‘s difference with Cloud Run?
Also you have some potential for saving money by over-provisioning your workloads on the actual compute instances, which is, as far as I can see, is not possible with Cloud Run.
This sounds super similar to Convox (generation 2 - built on top of AWS ECS). Is SetOps using Kubernetes (EKS) or ECS?
Earlier quoted context omitted.
Interesting thought. I can see your case for some growing companies. However I'm not sure if you would always need Kubernetes for this. What would you like adjust when we grow into a 1000 person company? I think you have still similar requirements like autoscaling, resource allocation, zero-downtime deployments etc. This is also possible without direct access to the container management. And there are a lot of compan…
> SetOps currently uses ECS Not everything is a stateless HTTP microservice. Solutions like ECS start to fall apart when you try to run stateful workloads, especially when the lifecycle of the workloads needs to be coordinated to prevent loss of availability or data (i.e. cannot tolerate 2/3 of the containers being knocked offline at the same time). AWS does not offer a managed datastore (e.g. RDS) for every datastor…
It's quite horrible in many ways but not I don't think any of it is really because the ECS model is somehow inherently unsuitable for stateful long-running workloads, it's Batch being a bad product.
Both ECS and Batch are just leaky abstractions enough that some unknown unknown or forgotten nuance will come along and bite you when you least need it and make you question the value proposition.
Crowded space! Flightcontroller, qovery, Architect. Competition is stiff, I am interested to see where your product is heading.
Also: https://getporter.dev/ https://convox.com/ https://atomizedhq.com/ And closely related: https://humanitec.com/ https://www.okteto.com/ https://www.env0.com/ And then old options like: https://dokku.com/ https://caprover.com/ And maybe: https://swarmpit.io/ https://coolify.io/ https://www.bunnyshell.com/ https://platform9.com/ And probably a dozen more. It's kind of wild.
Crowded space! Flightcontroller, qovery, Architect. Competition is stiff, I am interested to see where your product is heading.
That said, we believe that Coherence is unique in being integrated from dev all the way to production (it concludes cloud IDEs natively), being dashboard (vs CLI) based, and having a strong opinion about what environments types you need and how they relate to each other. This lets us reduce the CI/CD and integration work needed to use this on your team by 10x.
Similar to SetOps (which looks like an awesome product, btw) we don’t bet 100% on k8s as the only answer and believe in leveraging cloud-provided abstractions as much as possible. Agree with the sentiment that this is a big space and won’t have a winner-take-all outcome.
We’re in a closed beta, so if you’re interested in giving it a spin please get in touch!
BUT, it takes 24 separate commands to launch a "quick start" rails app. Hopefully this is just a alpha/beta experience, and the idea is get these going a little easier?
And once I launch it, what AWS resources are being used? How much should I expect this quick start rails app to cost me? Having a hard time figuring that out.
Earlier quoted context omitted.
I think you could anticipate my answer as a co-founder of SetOps :D
Why is your tool better than the others?
We worked hard to resolve the most common pain points when using the cloud in production:
For developers, we are the parrot on their shoulders: with our Production Readiness Check, you have the peace of mind that you didn’t forget something mission-critical for your production deployment. For example, we ensure that you configured backups for all your services, that you didn’t open unnecessary ports, and many other best practices. The Production Readiness Check is a smart checklist that analyzes your deployment. Much better than the compliance paper pile you usually deal with.
For the business people, we worked hard to offer accountability features missing from existing PaaS and cloud providers. Cost estimations are a core piece of SetOps so that developers see how expensive their deployment is. AWS sends you a hard-to-read invoice. Imagine getting a PDF from our monthly billing feature: it automatically tracks each client’s usage and calculates the cost accordingly.
I want to love this. I think we desperately need the "new heroku" and this touches on that. BUT, it takes 24 separate commands to launch a "quick start" rails app. Hopefully this is just a alpha/beta experience, and the idea is get these going a little easier? And once I launch it, what AWS resources are being used? How much should I expect this quick start rails app to cost me? Having a hard time figuring that out.
Regarding the AWS Resources being used: The cost estimation feature is on the roadmap, telling you how much exactly one Project costs. And showing you in advance how much more changes will cost.
Using SetOps starts with base costs since we need at least one EC2 instance + database running and some other services. The base costs are ~130$, including your first apps. But launching your first 10 containers doesn't bring many additional costs, so running some apps are quite cost-efficient.
Someone else already stated here that something is missing in the docs regarding the services provisioned in AWS. We will deliver that! For now, I can show you this slide from the internal pitch deck: https://static-media.setops.co/infra/aws-components.png
