Forum Moderators: open

Message Too Old, No Replies

help a newbie understand database architecture of big web apps

         

bwells

4:58 am on Jun 11, 2009 (gmt 0)

10+ Year Member



How do big, hosted web apps with many users (think basecamp, zoho) structure their databases? Does each user have a separate database, or do they share one database with unique table prefixes?

In the same vein, does anyone have good links / articles to help someone who knows the basics of PHP/MySQL (like me) learn about larger apps?

physics

2:06 pm on Jun 11, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hi bwells and welcome to WebmasterWorld.com!

This isn't an answer to your question exactly but you should definitely check this out if you're interested in large scale web app architecture. If you want to know about really big apps work look to Amazon:


# More than 55 million active customer accounts.
# More than 1 million active retail partners worldwide.
# Between 100-150 services are accessed to build a page.
...
It grew. For years the scaling efforts at Amazon focused on making the back-end databases scale to hold more items, more customers, more orders, and to support multiple international sites. In 2001 it became clear that the front-end application couldn't scale anymore. The databases were split into small parts and around each part and created a services interface that was the only way to access the data.

Right away you can see that Amazon's pages are really 'small pieces loosely joined' and they worry more about all of those pieces working properly than about specific database structures.
[highscalability.com...]

There are a lot of other articles on that site also.

bwells

5:40 pm on Jun 15, 2009 (gmt 0)

10+ Year Member



thanks for the link!