We're deploying thousands of tenants to their own postgres RDS instances which are completely overkill for most scenarios. On average we use about 3% CPU... We still do this because of three reasons: security isolation, performance isolation and monitoring. I think Aurora serverless will be a game changer for us, but we would still need per-tenant monitoring.
back
1 comments
I do this with a side project, except it's SQLite databases on s3 buckets -- that's about as easy as it gets and doesn't require nearly as much of the configuration overhead that Aurora does.
How does that work? Download DB file, read/write, upload DB file (if written)? What about concurrency?
I wouldn't trust it for write concurrency but it's been great for my use case (reads are multiple orders of magnitude more frequent than writes; and the writes can be queued), I'm using s3sqlite for this from the Zappa project: https://github.com/Miserlou/zappa-django-utils/blob/master/z....
How about performance? How much time to read from the database?