30k - 100k nodes in Umbraco 15

Questions
1

I landed a gig, I need to move 30k of news articles from Wordpress to Umbraco. Each node has 8 fields that I need to use.

I would use Umbraco 15 and Redis/Valkey for Hybrid Cache, but I am not certain will that perform well in backoffice? And it needs to scale to 100k nodes in next 10 years.

What do you think, can Umbraco handle this kind of nodes in single news Content Type?

2

My team recently migrated one of our client’s sites, which has over 200k nodes, from v8 to v13:
image

And the v13 backoffice feels surprisingly snappy, although 187k of those nodes are Media in my case.

I think Umbraco would be able to support that amount of content, but I would recommend:

  1. Make use of the List view option
    1.1. List View | Umbraco CMS
  2. Ensure that History Cleanup is configured
    2.1. History Cleanup | Umbraco Workflow
    2.2. Content history was one of the main causes of backoffice slowdown
  3. Don’t store all 100k news items under a single node
    3.1. Instead, organise them under seperate nodes, e.g. dates, to minimise the amout of direct children/sibling nodes
    E.g.
'News'/
├─ '2025'/
│  ├─ 'Janauary'/
│  ├─ 'February'/
│  ├─ 'March'/
│  │  ├─ 'News item'
│  │  ├─ 'News item 2'
├─ '2024'/
├─ '2023'/

Hope that helps :slight_smile:

3 Likes