I'm debating whether to go with a single global database for all users or to have a separate database for each user session. My concern is mainly about potential future issues with database architecture, especially if users come in and I struggle to migrate older projects that are stored in session-specific folders. I've successfully migrated single global databases before, but the thought of managing hundreds of session-specific databases is daunting. On one hand, using a global database could simplify migration. On the other hand, having separate databases might make it easier to manage user data deletion, which is important for compliance with EU privacy regulations. What do you think is the best direction for me to take? I'd love some advice on this!
1 Answer
It sounds like you're wrestling with a classic case of multi-tenancy! A lot of people advise going with the simplest solution that works for today rather than over-engineering for potential future issues that may never arise. It’s easy to get stuck in the mindset of preparing for every possibility. Your current setup might not fit all future needs, but that’s okay. Just back everything up regularly to ease your worry!
Thanks for the reminder! I keep backups daily, and that definitely helps me feel more secure about whatever choice I make.