Real-estate PHP application. Properties as class instances
<p>I hope I can ask this kind of question here, as I'd love to have the perspective and views of a fellow PHP developer.</p>

<p>I'm in the middle of completing a real-estate application using PHP. It uses RainTPL templating engine, and is considered purely object oriented.</p>

<p>I have a maximum of two derivatives for any base class, and I would also consider this application quite lightweight.</p>

<p>Anyhow, I have a PropertyManager class, that does just that. But, I am unsure if I should wrap every property prospect as a class in itself, or if the propertymanager should just use a elaborate database to return templated properties.</p>

<p>The reason for my question, is that I'm really tempted to create a class for a property, that the PropertyManager initializes an instance of for every property in a database.</p>

<p>However, as the number of properties can - with time - be anything from <strong>25 to 100</strong> in the database, I'm not sure how much it will slow down the server to handle instances for each and every one.</p>

<p><strong>Thus, I'd like to know if PHP and/or the average CentOS-based server can handle large amounts of class instances simoultaneously?</strong></p>

<p><strong>Edit:</strong> It might also be worth mentioning that the Property class would only have members that define the property (bedrooms, adress, google-map-url, image-directory), and no class instances.</p>

<p>Thank you, and sorry for the wall of text.</p>
