Overcoming the 1000+ node limit for cq:Page nodes in AEM 6.1
<p>We are currently building a large site using AEM 6.1 and will be migrating hundreds of thousands of records from an old RDMS-based system to AEM's JCR. We understand that the 1000+ node limitation does not apply to nodes with type nt:unstructured, but we are hitting limitation when using cq:Page nodes.</p>

<p>Our current site has a structure like this:</p>

<pre><code>/
├── blog/
│   ├── some-blog-post
│   └── another-post
└── articles/
    └── some-article
    └── another-article
    └── ...
    └── ...
    └── ...
</code></pre>

<p>We have over 6000 articles in the articles subtree, and we must maintain the URL structure for the consumer facing site. We are using the Classic UI and we of course are running into performance issues when you expand the articles folder in the AEM Siteadmin. We could afford to split the articles into additional directories in the Siteadmin, but we would have to maintain the flat structure for our URLs.</p>

<p>What is the best way to do this in AEM? We can't do this in the dispatcher because the dispatcher would have no way to know where to map the request in the JCR hierarchy.</p>