Per user projects/deployment with subhosting
I'm interesting in trying out an application architecture where each user account gets their own personal project/deployment/database using deno deploy subhosting. When a user registers, it would create a project and deployment, with their own KV database. This would enable per user isolation and rate limiting, as well as potentially allowing per user customizations.
I'm curious if anyone has tried an approach like this and how happy/successful it was and if there's any gotcha's I haven't thought about.
One gotcha that I already ran into is that in the documentation, it looks like wildcard subhosting all has to go to the same deployment. So for example, if I wanted user-a.example.com and user-b.example.com as per user project/deployments it wouldn't actually work. It says "coming soon" that you'll be able to, though. I'm curious if anyone has an estimate for that as well.
Thanks in advance for any help!
0 Replies