Databases
StackOverflow2013
Postsdbo
POUser produced site content, potentially massive dataset - Zope/Plone or Django?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUser produced site content, potentially massive dataset - Zope/Plone or Django?
    primarykey
    data
    text
    <p>I am looking to produce a site similar to a venue "What's on" site.</p> <p>The plan is that the venues can register an account to the site and then through their own 'admin' section upload/post all their latest events that are on. I am hoping that very large number of venues will sign up and each have a large number of events thus producing a very big dataset. </p> <p>I then want end users to be able to search all the venues which have a particular type of event through the site, and also importantly via mobile iphone/android applications.</p> <p>I am initially hosting this system on a resource limited VPS which I have to scale up all factors in order to 'upgrade' (I can't just whack loads of RAM in without paying for extra bandwidth/disk space/etc. too), but I do plan to upgrade as required.</p> <p>After much research, the two best options I am looking at for implementation are Zope/Plone or Django+PostgreSQL (site from scratch), neither of which I have used before.</p> <p>My question is, in people's experience, '<i>What is most appropriate for this kind of site platform and dataset.</i>'</p> <p>I can afford to put in much of my time learning either of these from scratch, but I can't afford to have to change and start again from scratch with a different framework.</p> <p>So to summarize I am aiming for (please let me know if it's unrealistic):</p> <ul> <li>Low initial cost. (In trade for time input)</li> <li>A venue user admin section for data addition.</li> <li>A user Login to post reviews/comments.</li> <li>Scalable.</li> <li>Ultimately large dataset.</li> <li>Runs fast on limited resources.</li> <li>Use a future-proof framework.</li> <li>Relatively easy to maintain/extend data model over time.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USIAmFledge
    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. This table or related slice is empty.
    1. CODid this site ever take off? If so, where is it?
      singulars
      1. POUser produced site content, potentially massive dataset - Zope/Plone or Django?
      1. UStesserakt
    2. COProduction on it didn't start, but still may well do. Only thing is, as ever, Google have done something similar since!
      singulars
      1. POUser produced site content, potentially massive dataset - Zope/Plone or Django?
      1. USIAmFledge
 

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