Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I can't believe anyone would do separate databases.

Just wait until a migration doesn't run on 2 of your 400+ customer databases. Or multi-hour migrations.



When all customer data lives in the unified database: Just wait until a bug in a query exposes the data of customers to each other, creating instant regulatory and privacy nightmares for everyone.


With an orm and customer objects to create scoped queries, I haven't found this to be a problem. It's also very easy to check in code reviews. And not a painful issue from, well, the lack of this happening given it's an extremely common app design.


Sounds good to me. Now you've got 398 happy customers on the new version, and a small scale issue to resolve with two customers.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: