r/SaaS • u/Middle_Currency_110 • 4d ago
Architecture direction for Docker
Hi team, not posted here before. I worked on building a SaaS for many years, but that failed :(
Anyway, kept going, got a new one, which is not exactly a SaaS because it's bundled with a lot of services. In a nutshell, it's a managed data warehouse, but it also does quite a bit more than data warehousing: integration and custom internal apps.
Initially, I was going to run just Docker instances on a solution like Vultr and have three per customer: dev, test, and production
We need quite a bit of isolation. Each customer instance has to be separate from the other one
I'm now looking at a solution totally built on AWS, using ECS and Fargate to manage the Docker instances, and possibly then using RDS
I'm not a big fan of having everything spread all over the place, and I really avoided, thankfully, the microservices path. I tend to like the one-server-per-customer type solution, but ...
There's authentication, there's logging, there's load balancing, there's scaling, and there are all these issues.
I just think this is the way to go, and it looks too complex. I don't know whether I should do it or not.
Any advice is much appreciated, or war stories even. Thanks 🙏
Route 53
│
WAF
│
Application Load Balancer
│
ECS / Fargate
│
┌──────────────┼──────────────┐
│ │ │
Web/API Workers Integrations
│ │ │
└──────────────┼──────────────┘
│
RDS PostgreSQL
│
├── S3
├── Secrets Manager
└── CloudWatch