Databases
StackOverflow2013
Postsdbo
POOne big MySQL DB or a thousand little SQLite databases?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOne big MySQL DB or a thousand little SQLite databases?
    primarykey
    data
    text
    <p>I am working on a Web based organisation tool. I am not aiming the same market as the wonderful Basecamp, but let's say the way users and data interact look like the same. </p> <p>I will have to deal with user customisation, file uploads and graphical tweaks. There is a fora for each account as well. And I'd like to provide a way to backup easily each account.</p> <p>I have been thinking how to create a reasonable architecture and have been trained to use beautifully normalized data in a single (yet distributed if needed) MySQL DB. Recently I have been wondering : is it possible to think about using one SQLITE DB to store the data for each account and only use MYSQL for the general web site management ?</p> <p><strong>The pro :</strong></p> <ul> <li>backing up is straightforward : set version, zip, upload.</li> <li>don't bother if each account use a massive fora : the mess is in one file for every one of them.</li> <li>SQLITE is lightening fast, no expensive connection time...</li> <li>Table scheme is much simplier : no need to make any distinction between account every times</li> </ul> <p><strong>The cons :</strong></p> <ul> <li>don't know if it's scalable</li> <li>don't know if the hard drive will keep up</li> <li>don't know if there is a way for SQLITE to not be stored in RAM since it would be quickly a disaster</li> <li>lots of dir and subdirs : will this be ok ?</li> <li>maintenance issue : upgrading the live site means upgrading all the db one by one</li> <li>dev issue : setting a dev / pre prod / prod env will be quite hard</li> <li>commom data will still require using mysql, so we would end end with 2 DB connections for each page, arg</li> </ul> <p>More cons that pros, still, it makes me wonder (zepplin style).</p> <p>What do you say ?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAlex Fort
    1. USe-satis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOne big MySQL DB or a thousand little SQLite databases?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POOne big MySQL DB or a thousand little SQLite databases?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POOne big MySQL DB or a thousand little SQLite databases?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COah, a thousand points of SQLite...
      singulars
      1. POOne big MySQL DB or a thousand little SQLite databases?
      1. USJason S
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload