They charge for a premium plan, as per the article. We pay for a premium plan at our company.

Fargate isn't really expensive? It does have a premium but I wouldn't say 'really expensive'. https://www.trek10.com/blog/fargate-pricing-vs-ec2

> It does have a premium but I wouldn't say 'really expensive'

EKS Fargate costs $29.55 per 1 vCPU and $3.25 per 1GB of memory per month. This is listed in their official docs: https://aws.amazon.com/fargate/pricing/

Let's say you plan to run 5 web apps, 3 replicas of each and they all need 4gb of memory.

Fargate demands you reserve 2 vCPUs for 4gb even if your app only needs 20% of 1 CPU, so you're wasting 1.8 CPUs per replica of each app. Often times web apps use a lot more memory than CPU, even with Ruby or Python your web app might be humming along at like 5% CPU load while using potentially gigs of memory.

That leaves you paying:

    5 * 3 * 4gb of memory = 60gb of memory = $195.00
    5 * 3 * 2 cpus        = 30 cpu cores   = $886.50
                                           = $1,081.50

You're wasting a ton of CPU here because of AWS' rules on EKS Fargate memory / cpu size combos.

To run your workload on EC2 you can grab yourself (4) m6i.xlarge instances which has 16 CPU cores and 64gb of memory of total capacity which is $560.64 (grand total for 4).

In this case Fargate is double the cost, to me that is a lot. You do have less CPU capacity but it doesn't matter, your apps aren't coming close to that in CPU usage.

If your work load supported it (stateless web apps that can finish a request within 2 minutes) you could use EC2 spot instances too which would be $122.35 total instead of $560.64.

Both regular instance and spot instance prices were taken from AWS' official docs, I just multiplied their hourly values by 730 which is how many hours AWS uses to calculate 1 month.

From a few years ago? We have used managed ES for a while now and see no issues however I realise its different for everyone.

AFAIK with Fargate a lot of this is handled for you, as long as you have the auto scaling group.

We have this setup with two capacity providers (FARGATE_SPOT and FARGATE) with a 75/25% split, meaning that even if there are no spot instances available we will still be up.

The benefit of Fargate being that we don't need to care if certain instance sizes are not available as that is handled by AWS.

Cool, when fargate launched they didn't have a spot possibility (AFAIK) and since we run ECS on Spot instances it would just be a massive increase in cost to switch to FG, but if it now can use underlying spot instances, it might be worth looking at again..

Yeah spot capacity providers for Fargate only got added a few months ago, been running well for us in production.

All of which you get with Gitlab plus a first class CI/CD system out of the box and a more popular (read familiar) interface which reduces the friction for new developers to get started with KDE.

We perform manual testing and qualification on feature branches (but deployed to a qa or staging environment).

The thing that really helped us was separating the idea of environments and branches.

Easyjet have been a main airline within the UK for many many years. They may be struggling because of the current environment but this isn't a small operation who wouldn't have a security team.

Looks nice! We have been looking at improving our sprint planning process and going to try this out today (instead of our typical spreadsheet!)

I hope you like it! :)

We don't see that and use Meet (via GSuite) to have external calls with people and have never heard that that require a Google account.

Because the paid G Suite behaves different than the free Meet they announce now. Makes sense, because external dial (via phone) costs them money.

So given a web server, what language can 'come close' to the ease of deploying with PHP?

Unless your only experience is 1999 style FTP with shared hosting and you've never used anything else, I don't know how you can claim that `node server.js` or running your Cargo-built server.exe is somehow harder or more complicated.

For example, PHP is complicated enough that people use WAMP/MAMP.exe just for local development.

"Given a web server" seems a pretty big caveat. I'm not a big node cheerleader (even though I work in it day to day), but it doesn't need to be given a web server to achieve the rest of this claim.

I'm a mostly PHP dev, but with apps in other languages, all you need more is a systemd unit file to start the app? (ruby, nodejs, go, etc)