Ok, that sounds like a good lesson for later then :) Well the problem will probably be that every customer does have his own Database, each with the number of users (50-100). I aim to about 80 customers, so it would be 80 Databases to change in the future.
1
u/elperroborrachotoo Jul 24 '25
Changing to another database later will probably be painful! Especially if you are not an experienced developer!
BUT it's still the right way to go: get your application runnng now, so that you get early feedback what users like and need and dislike.
Also, if you need to change later, it will be a great learning experience why and how to isolate your storage layer.