latebird22 (u/latebird22)

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.

latebird22 commented on Show HN: SetOps – Run containers, databases and more in your own AWS account setops.co/... · Posted by u/latebird22

oakct · 4 years ago

Nice project! Just a note of feedback: for a service that advertises with transparently deploying resources to my own AWS account, it is surprisingly difficult to find out to what AWS services the various concepts in setopts maps to. Given that I would be the one paying for any mishaps and overprovisioned resources, it would be good to have a reference for this. Maybe I missed it?

latebird22 · 4 years ago

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.

I can share a slide of one of our presentations right now which roughly shows the inner workings of SetOps in your AWS account: https://static-media.setops.co/infra/aws-components.png

latebird22 commented on Show HN: SetOps – Run containers, databases and more in your own AWS account setops.co/... · Posted by u/latebird22

codegeek · 4 years ago

I donno. I am looking for a simpler solution on top of AWS that abstracts away setting up the services with configuration but doesn't necessarily use containers for everything and def. not Kubernetes.

Is this not desirable for others ? All the solutions that I see are focussed on containerizing (I get that to an extent). But I would personally want a service on top of AWS that abstracts away setting up EC2, load balancers, auto scaling, RDS etc etc. Does it have to be kubernetes ?

latebird22 · 4 years ago

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.

latebird22 commented on Show HN: SetOps – Run containers, databases and more in your own AWS account setops.co/... · Posted by u/latebird22

superb-owl · 4 years ago

Here's a few examples of policies/needs that I've seen companies run up against at scale. K8s does a great job solving them.

* Understanding which workloads share a node's memory/CPU, and isolating certain workloads for security reasons

* Running specific workloads on specific instance types (e.g. with GPU or extra CPU)

* Configuring network policy between workloads

* Airgapping certain workloads

* Setting priority levels for different workloads, so some scale more rapidly while others have to wait for a new node to be provisioned

* Customized scaling behavior (e.g. based on the depth of a queue or latency metrics)

* Multi-region support for DR

I could probably go on :)

latebird22 · 4 years ago

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.

latebird22 commented on Show HN: SetOps – Run containers, databases and more in your own AWS account setops.co/... · Posted by u/latebird22

_whiteCaps_ · 4 years ago

Have you seen https://github.com/cloudfoundry/cf-for-k8s?

latebird22 · 4 years ago

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.

latebird22 commented on Show HN: SetOps – Run containers, databases and more in your own AWS account setops.co/... · Posted by u/latebird22

superb-owl · 4 years ago

> Isn't it just Kubernetes under the hood? That's not the right question...Kubernetes is just one of the building blocks for easy and secure app deployment. It is not a one-shot answer for day two operations such as reliable databases, load balancing, backups, certificates, and data security...With SetOps, you don't need to care how we run containers – you'll profit from the sensible choices and long hours our infrastructure experts spent to make sure it runs well.

I have really mixed feelings about this response.

On the one hand, I 100% agree - vanilla k8s is not prod-ready, and you need to do a _lot_ of work to figure out some things, especially around persistent storage (but load balancing and certs are a pretty solved problem).

But the line "you don't need to care how we run containers" bugs me. Maybe your two-person start up doesn't need to know, but eventually you will grow to the point that you _do_ need to care how things are running, and need control over it. This is why so many companies end up outgrowing Heroku and have to go through an expensive migration.

What I'd love to see is a "batteries-included Kubernetes", which allows me to slowly take control over more and more of the stack, until I'm a 1000 person company and ready to run my own clusters.

latebird22 · 4 years ago

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.