New project with lot's of pages

I need advice:

I’m working now on a huge project with lot’s of pages, lot’s of TVs, some custom php code (in snippets) under EVO 1.0.4. (pages are relatively small, only few lines of text, something like job portal).

In first 2-3 months I’m not expecting more than 2-3000 documents, but in future, there will be much more (tens of thousands).

Should I consider REVO as a solution for future development or I will need to start form zero on custom platform?
If REVO will fulfill my needs, what about migration? Is a database the same?

Thanx in advance
Ivan

I would definitely consider Revo for development. Seeing the (expected) number and nature of your data/entries i wouldn’t choose a resource based structure though. There has been some debate on this, http://modxcms.com/forums/index.php/topic,18872.0.html , but in your case it seems clear that having a resource for every job/entry would be less than ideal and could lead to performance and maintainability issues in the long run.

It would be best to leverage MODx as the Content Management Framework it is and develop your own component which is geared towards your needs. Using your own database schema and the modx api and xpdo you can make your own ’application’. Using custom manager pages you can create a UI for it right inside the Revo interface. A resource can serve as the view for your job data.

Plz note that i myself haven’t developed anything like that in Revo but it should be where Revo shines.

With large numbers of data records, it would be best to put these into their own custom tables. You create a resource in Revo to act as the view and create a snippet or a couple snippets to do the queries and set the placeholders for that view. In addition it’s apparently pretty easy to build a custom 3rd party component to view and edit the records.

There is a loose tutorial over at http://docs.modxcms.com (I’d link to the article but at the time of this writing the server is having issues (we are working on a permanent solution to that))

Cheers,

Jay

Thanx Guys,
I spent lot’s of time searching and reading many forum posts about my problem and as far as I know, one Russian crew tried to optimize MODx cache (core hack), they managed to work with 50.000 documents in tree but with huge memory consumption per connected visitor (and I’m expecting 2-3000 visits per day in beginning).

So, I don’t think that in near future MODx will support huge amounts of documents, and I have to go back to your solution:

- create new database table for my data
- create snippets for showing data
- create module for inserting new data
- create module for newsletter depending on webuser config (every webuser will get only desired categories on email)
- create snippet for showing last 20-30 new inserts in database
- create module for searching through records in database
- create ...
- create ...

but in that case, why to use MODx, almost everything will be custom, except that I can use MODx API instead of writing all database management functions from zero? With separate database table, I’m losing almost all features of MODx I need (data is displayed through DITTO and search is done through ajaxsearch snippet).

I have no problem with document tree in manager, I will not use tree to manage documents.

Also, I’m not sure that database is problem, what’s different in using new table for data instead of current table (most of data is in TV’s, in document I have only title, longtitle, alias, and in content is one snippet call...).
In TV’s I have few words only, no pictures, no rich text,...

Second problem: I’m not a PHP developer, and doesn’t have budget to hire a PHP programmer who can do this project form zero, so, I’m forced to use MODx until my projects start to make money...

Developers, please, fix a cache problem and MODx will be more than just good CMS for small projects.

If you have any ideas or suggestions, I will be glad to hear...
Thanx in advance.

P.S. smashingred, SiNNuT: I didn’t have a chance to try your solutions in REVO...Will do my best to check in in next few days.

Sorry if this post is a little confusing, but, believe me, I’m confused too...

I have created new table for documents, now I’m working on module for documents manipulation (insert,delete,edit records)...

MODx will be used form users management, database API, search (I’m trying now to use ajaxsearch to search only through on my new table)...

If someone has any experience with project like this, I would be glad to hear any suggestions, guides, tips...

Thanx