Hi there! I've been managing a bare metal k3s setup for my solo SaaS project for about a year and a half now. Initially, I was aiming to deploy on AWS using managed services, but my contractor advised against it, claiming it would be too costly and that the customer service wasn't great. Looking back, I wish I had trusted my instincts rather than following their advice. Now, I'm wondering if moving to AWS EKS, Fargate, and RDS would be worth it. Currently, I have around 25 pods running, including frontend, backend, celery, postgres, redis, grafana, and more for both staging and production. I'm getting the hang of managing k3s, but I'm curious if the migration could lessen my workload, especially since I have some paying customers now. Any thoughts on whether making the switch would be better in the long run?
3 Answers
If you’re not facing strict compliance needs, sticking with k3s might be the way to go. Using RDS could automate some backup processes, but the effort and time you save might not be significantly less, and there’s a chance it could even increase. It’s good to hear you're working on mastering your stack!
Honestly, it all comes down to how you value your time versus costs. While AWS services can offer convenience, you'll still need to put in some effort to configure them properly. A bad setup could lead to unexpected expenses. That said, many aspects of what you've learned with k3s will still apply, which could make the transition smoother.
Your current setup with 25 pods isn’t that large, so switching to AWS services like RDS or Amazon’s managed solutions could enhance reliability and scalability. However, it comes at a cost and potentially locks you into their ecosystem. If you go for it, I'd lean towards using RDS over hosting Postgres yourself; at small scales, self-hosted Postgres can be a bit tricky.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures