eldan88 Posted April 22, 2012 Share Posted April 22, 2012 I am currently creating a database for a food online ordering websites that going to be used for multiple restaurants to have their menu on. My questions is. What will be more efficient A) To create a one database that will store all the menu items, check out info, etc for all restaurants B) To create a separate DB for each store Thanks! Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/ Share on other sites More sharing options...
Barand Posted April 22, 2012 Share Posted April 22, 2012 If this is a system for several totally independent restaurants then I'd keep the data separate. On the other hand, if this is for a chain of restaurants and at some point you will need to produce reports for the entire group then there is a good case for a single database. Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1339678 Share on other sites More sharing options...
eldan88 Posted April 22, 2012 Author Share Posted April 22, 2012 If this is a system for several totally independent restaurants then I'd keep the data separate. On the other hand, if this is for a chain of restaurants and at some point you will need to produce reports for the entire group then there is a good case for a single database. But i have a question on that. My developer said that if we do separate database for each restaurant its going use a lot of system resources and slow down the server. Is that true? Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1339683 Share on other sites More sharing options...
ignace Posted May 1, 2012 Share Posted May 1, 2012 But i have a question on that. My developer said that if we do separate database for each restaurant its going use a lot of system resources and slow down the server. Is that true? Apparently you have every confidence in the developer you hired! Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1341875 Share on other sites More sharing options...
awjudd Posted May 1, 2012 Share Posted May 1, 2012 There is no need to go a separate database for each restaurant. In fact, that is not only overkill but a very bad idea. A relational database would definitely do the trick. ~awjudd Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1341903 Share on other sites More sharing options...
ignace Posted May 1, 2012 Share Posted May 1, 2012 Can you elaborate why you think this is a bad idea? Because having a separate DB for each restaurant makes it easy to scale it in the future (for example all low-volume DB's on one node) where-as one DB means you need to replicate ALL the data over multiple nodes regardless of high- or low-volume websites. Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1341923 Share on other sites More sharing options...
Jessica Posted May 1, 2012 Share Posted May 1, 2012 But i have a question on that. My developer said that if we do separate database for each restaurant its going use a lot of system resources and slow down the server. Is that true? Apparently you have every confidence in the developer you hired! What's wrong with getting a second opinion? Do you blindly trust people you hire without doing your own research? If so, I have some ocean front property for sale. Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1341929 Share on other sites More sharing options...
ignace Posted May 1, 2012 Share Posted May 1, 2012 It was sarcasm! But you make a good point, and sure, getting a second opinion IS a good thing IF that person is qualified, not so sure about the kind of confidence you should put in an anonymous internet user. You also make my point: If so, I have some ocean front property for sale. Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1341932 Share on other sites More sharing options...
fenway Posted May 12, 2012 Share Posted May 12, 2012 Multiple databases are really annoying -- unless you're dealing with Big Data. Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1344966 Share on other sites More sharing options...
Barand Posted May 13, 2012 Share Posted May 13, 2012 ... whereas a single database for several clients, each with different requirements, is a dream? Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1345094 Share on other sites More sharing options...
The Little Guy Posted May 14, 2012 Share Posted May 14, 2012 ... whereas a single database for several clients, each with different requirements, is a dream? if it is built properly. Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1345424 Share on other sites More sharing options...
fenway Posted May 19, 2012 Share Posted May 19, 2012 ... whereas a single database for several clients, each with different requirements, is a dream? Of course not -- but I've seen multiple databases be much worse. Link to comment https://forums.phpfreaks.com/topic/261436-creating-a-db-for-restaurant-online-ordering-website/#findComment-1346839 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.