|
|
|
|
|
by lelanthran
1072 days ago
|
|
> And if your MBP were to die today? Or if a burst of traffic came through? Or if you closed the lid and forgot to turn Caffeinate on? So ... two macbooks then? > Surely you can understand why people don't routinely host all their project's infrastructure on their laptops, even if the technical specs are enough. I think the poster was simply highlighting that 150GiB of storage, 6TiB of transfer and around 4 requests per second to an average of maybe[1] 26 users per minute might not necessarily need a K8 cluster and 8 different cloud services. [1] I'm taking "thousands of users" to mean "up to 19000", otherwise they would have said tens of thousands, dozens of thousands, etc. |
|
But even then, you’re just pushing the cost onto the person maintaining the system.
Cloudflare R2 => Now you have to bootstrap and maintain your own high availability Minio cluster. On multiple servers in multiple data centers for redundancy, of course.
Cloudflare Workers/Pages => Now you have to maintain your own compute runner (granted, could be as simple as a docker container but that still both requires work to set up and transition over as well as maintain over time) and load balancer (once again, just Nginx or Apache but that requires setup and maintenance) to execute and serve this content.
Cloudflare Access => Now you have to maintain your own access control system like ory.
Cloudflare Tunnels => If you’re only running one node, this isn’t needed, so congrats I guess. You’d still need to provide internal access if you have multiple nodes in a HA environment, though.
AWS EC2 => Now you need to maintain your own VMs.
Etc.
This is a volunteer project. Having someone maintain all these things may not be even remotely practical.
It’s all the rage to hate on cloud services in 2023 but they abstract away a lot of operational work and that’s not something to be blindly discounted.