1,745 karma · joined October 14, 2018
Also working on AI Employees: https://Geta.Team
We support postgres but also MySQL, redis, opensearch, Clickhouse and many more.
About backups we offer differential snapshots and regular dumps that you can send to your own S3 bucket
https://docs.elest.io/books/databases/page/deploy-a-new-clus...
You stop worrying about S3 vs EFS vs FSx, or Lambda cold starts, or EBS burst credits. You just deploy a Docker stacks on a fast NVMe box and it flies. The trade-off is you need a bit more DevOps discipline: monitoring, backups, patching, etc. But that's the kind of stuff that's easy to automate and doesn't really change week to week.
At Elestio we leaned into that simplicity, we provide fully managed open-source stacks for nearly 400 software and also cover CI/CD (from Git push to production) on any provider, including Hetzner.
More info here if you're curious: https://elest.io
(Disclosure: I work at Elestio, where we run managed open-source services on any cloud provider including your own infra.)
can you give some numbers? or at least ballpark?
I once explored this, hitting around 125K RPS per core on Node.js. Then I realized it was pointless, the moment you add any real work (database calls, file I/O, etc.), throughput drops below 10K RPS.
Saying 'fuck responsible disclosure' is basically saying 'let’s hurt innocent users until the company caves.' That’s not activism, that's collateral damage.
If someone genuinely cares about accountability, there are legal and ethical ways to pressure companies. Dumping 0-days into the wild only helps criminals, not users.
While I understand that the author attempted to contact Monster without receiving a response, publishing details of the vulnerabilities and how to exploit them only puts users at greater risk. This approach is reckless and harmful.
Apple are by far the worst offender and I can't wait for Safari to die
You would "scale" better with a $5 vps
Title: Serverless is eating Kubernetes—and that's a good thing
After 6 years of watching K8s engineers over-engineer themselves into a corner with YAML spaghetti, I finally moved a production workload to AWS Lambda + EventBridge + DynamoDB. You know what happened?
Nothing broke. It just worked.
No Helm charts. No Ingress hell. No cluster upgrades at 3am because of CVEs in some sidecar no one uses anymore. The whole app is now ~300 lines of infra code and it scales from 0 to 10k RPS without me touching anything.
Meanwhile, the K8s crowd is still debating which operator to use to restart a pod that keeps crashing because someone misconfigured a liveness probe. Or building internal platforms to abstract away the abstraction they just built last quarter.
Remind me again what the value-add of Kubernetes is in 2025? Other than keeping a whole cottage industry of "DevOps" engineers employed?
Serverless isn’t the future. It’s the present. And K8s? It’s the next OpenStack—just slower to die because it has better branding.
I don't see how it could be worst, any other gov in Iran would be better for the world and for the peoples in Iran.
Are you genuinly thinking that giving nuclear weapons to terrorists is a good idea?