1,466 karma · joined January 30, 2016
- ALBs -- yeah this is correct. However ALBs have much longer startup/health check times than Envoy/Traefik
- Cloudwatch - this is true, however the "configurable" behavior makes cloudwatch trash out of the box. you get i.e. exceptions split across multiple log entries with the default configure
- ECS tasks - yep, but the failure behavior of tasks is horrible because there're no notifications out of the box (you can configure it)
- Fargate does allow you to avoid maintenance, however it has some very hairy edges like i.e. you can't use any container that expects to know its own ip address on a private vpc without writing a custom script. Networking in general is pretty arcane on Fargate and you're going to have to manually write and maintain the breakages from all this
> You might be able to do the same with Kubernetes, but your control plane will be out of date, your OSes will have many missed security updates. Might even need a major version update to the next LTS. Prometheus, Loki, Tempo, Promtail will be behind. Your helm charts will be revisions behind. Newer ones might depend on newer apiVersions that your control plane won't support until you update it. And don't forget to update your CNI plugin across your cluster, too.
I think maybe you haven't used K8S in years. Karpenter, EKS, + a GitOps (Flux or Argo) makes you get the same machine maintenance feeling as ECS but on K8S without any of the annoyances of dealing with ECS. All your app versions can be pinned or set to follow latest as you prefer. You get rolling updates each time you switch machines (same as ECS, and if you really want to you can run on top of Fargate).
By contrast, if your ECS/Fargate instance fails you haven't mentioned any notifications in your list -- so if you forgot to configure and test that correctly, your ECS could legitimately be stuck on a version of your app code that is 3 years old and you might not know if you haven't inspected the correct part of amazon's arcane interface.
By the way, you're paying per use for all of this.
At the end of the day, I think modern Kubernetes is strictly simpler, cheaper, and better than ECS/Fargate out of the box and has the benefit of not needing to rely on 20 other AWS specific services that each have their own unique ways of failing and running a bill up if you forget to do "that one simple thing everyone who uses this niche service should know".
Because as annoying as getting the prometheus + loki + tempo + promtail stack going on k8s is —- I don’t really believe that writing it from scratch is easier.
i.e. you have a set of kubernetes CRDs probably managed by a gitops solution -> we do this for you, you have a bunch of different pyproject.toml files that need to be orchestrated into a docker container -> this is what that looks like in release, tbh our terraform isn't a huge bottleneck because so much just ends up going in the kube crds.
maybe have two pitches: 1 for startups getting started and 1 for startups who already have a lot of this figured out (probably your bigger target audience if you have a strong pitch)
Not trying to be negative, but I think there may be a 30 second pitch to be made to people like me that isn't made on your site.
Your hypothesis is essentially that Bloomberg, as a company, doesn't make sense.
At $0.99 a year for each ycmpbinator and ycpmbinator, and the way inflation is going — I think I should be saving over $10k a day by the early 30s.
I'm not convinced it will happen either. Venture Capital operates on a business model that is really hard for human intuition to deal with. 1/1000 success rates require so few break out successes that, yes -- they can fund an entire sector that will, with extremely high probability, fail and still be profitable.
It just doesn't matter. Vim is objectively faster. I don't care how many millions of dollars or pl optimizations my editor has. I care how quickly it works.
You can just open both editors next to each other and ask how they are. For me, it's trivial to see that vim is at least an oom faster than VSCode. I don't need to profile or show test coverage. I can just use it and it works. Even if they were about the same speed, the less-than-perfect vim mode implementation always takes too much time out of my editing flow.
Occasionally, an ide will have such a great curated experience that I'll use it for something specific -- but the general case is a no contest for me.
I also wouldn’t be betting on US terrestrial internet providers to outcompete anything.
Do you believe that Russia benefits equally from the election of either candidate this time around?
Also, https://en.wikipedia.org/wiki/List_of_Russian_assassinations
And they have repeatedly been caught meddling directly in Western countries (see i.e. multiple assassinations in the West).
https://www.airandspaceforces.com/article/unmanned-flying-te...
Maybe there’s a complex solution here, but the naive one of global compliance to local demands needs an evaluation of cost vs reward. There’s also the somewhat possible concern that the EU might actually just be hostile to Apple and cutting losses now against possible future losses makes sense. (Again, remember we’re presuming order of magnitude increases in fines).