Quote from: BYsoft at Feb 11, 2010, 06:14 PM
Ryan has stated http://bit.ly/ahcEqf the 5000 page limit is ’entirely dependent on how your server is configured’. My site has pages in the 10-20k range. How can I configure my articles and listings? Where can I read more about configuring my server to handle this?
I would approach this as how many distinct views do I need to create, and separate this from the actual large quantity of articles you are publishing. MODx Resources (aka Pages) do not necessarily correspond one-to-one to an "article" you publish, and in fact, as the quantity of articles go up, the more important it is to model a dynamic site in terms of distinct, dynamic views, rather than the total quantity of your content or data you’ll be presenting in these views.
IOW, you can have a custom database of articles, and create one MODx Resource that accepts a parameter indicating which article is to be rendered in the MODx Resource. This keeps the overhead of the entire site at the lowest common denominator, and transfers the responsibility for serving, caching, and generally dealing with the large quantity of data to the one view, where it belongs. This means you would need a custom admin UI for managing your articles, outside of the MODx Resource tree, but is IMO the only way to approach high-traffic dynamic sites with large quantities of similar content items.
Quote from: BYsoft at Feb 11, 2010, 06:14 PM
Working with a team at an established magazine in print and online. Transitioning our content to a new CMF. Is MODx currently being used for large revenue driven applications?
Could somebody list some examples? Is MODx proven with big sites?
I’ll let the marketing team respond to this.
Quote from: BYsoft at Feb 11, 2010, 06:14 PM
Can we build the site in Revolution and run it on Evolution if the Beta isn’t RC by the time we need to go live?
Probably not; Revolution is a complete rewrite of the MODx Evolution code-base and the differences are quite significant. If you target Revolution, your code will be object-oriented and abstracted from the database. Evolution depends on direct MySQL queries and a legacy API that would not handle code written for Revolution.
What kind of estimated traffic does the site expect? This is an important question; MODx Evolution is a little faster out of the gate, but will not scale to the extent that MODx Revolution will as the amount of content and/or traffic increase, and is infinitely easier to deploy in a load-balanced or cloud environment. It also has a lot more built-in features such as memcached cache support, database result set caching, etc., as well as a multitude of new ways to customize various aspects of the core, including allowing custom session handling classes, cache handling implementations, error handlers, and much more, all of which contributes to its ability to scale.
I hope that helps clarify some things and if you have any further questions, feel free to ask and we’ll do our best to steer you in the right direction.
☆ A M B ☆
MODX Staff
MODX Staff