• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
How to structure database(s) for larger applications?

#3
[eluser]Matthieu Fauveau[/eluser]
Hi Skinnpenal,

Basically there is 3 ways to go (from my point of view) :

1. Each customer gets is own database. More secure (customers data are not vulnerable to potential bugs in your code that could compromise privacy of data), but more difficult to update (you'll have to update all the database and that could be an issue with a certain amounts of customers)

2. Use a shared database. Easiest to maintain but need more focus on the code security to make sure data are kept private (require more testing to find potential vulnerabilities in the code).

3. Use "views" to achieve separation of customers data. Probably the way that will cost the less. Unfortunately in their current state MySQL's views are not very reliable and they do not update automatically when you change the parent table. So we are back to point 1 in regard to maintability/updatability. Still, this seems to be the best way if you are willing to use let's say DB2.

4. Use stored procedures. But I'm pretty much a newbie on that subject and I'm still not really sure how to do it.

Hope this little input will help you make a choice. I personally go for the point 2. Sure I spend more time on the code but I feel it's worth it.


Messages In This Thread
How to structure database(s) for larger applications? - by El Forum - 06-23-2008, 01:55 PM
How to structure database(s) for larger applications? - by El Forum - 06-23-2008, 02:50 PM
How to structure database(s) for larger applications? - by El Forum - 06-23-2008, 03:02 PM

Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2020 MyBB Group.