First of all Cloud Run only provides the workload / container part of an application. SetOps also does more like managing databases, storage, backups, monitoring, network security, etc.
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.
Thank you so much for your feedback. You are not mistaken – it looks like our documentation is currently lacking some of these details. We are going to improve on that within the next days.
That's exactly the idea with SetOps: using all these components under the hood but abstracting it for the user with a much simpler management. You could give it a try in the demo environment if you like.
You are totally right. For these specific use cases you probably want full control. :) I guess if you have these requirements a tool like SetOps, which simplifies the management, might not be the right fit then.
Although some of these requirement, like running specific workloads on specific instance types, could easily be implemented.
My experience with tools like these on Kubernetes, even with something stable and widely used as e.g. certmanager, is that in the end something still breaks and you still need to get familiar with all the building blocks. In comparison if you use managed services like the AWS Certificates service you have less friction and less risk for something to break.
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 companies which do not become the next Unicorn and need an easy way to manage their container workloads.
SetOps currently uses ECS since it comes with no additional overhead costs for the management plane/API and does the container management job well enough. However this is not a definite decision and ECS could be replaced in the future. The main point is that there is a simple abstraction for users managing the workloads and that the "backend" is interchangeable.
