DEV Community

Discussion on: I built a large production static site for a publisher (100K articles) [without GatsbyJS], Ask Me Anything!

Collapse
 
cjbrooks12 profile image
Casey Brooks

If you were to redo this site today, knowing what you know now about your build process, what would you do differently? Would you use an existing SSG, or make the build pipeline yourself?

Collapse
 
jjaybrown profile image
Jason Brown

One problem I see with existing SSG is incremental builds, particularly when it comes to JS. So build performance would need to be really good, we feel we still have that with what we have, we had issues scaling resources to process more content, so I would probably change the language of the pipeline to something more suited towards concurrency and better resource management.

What we didn't know was that we'd have 100K articles. So scaling became a linear problem. More resources = more articles generated.

Scaling memory is painful for nodeJS.

With everything being React nowadays, definitely using a tool or framework that supports SSR for React.

We also suffer a lot from chained processes, so moving towards a more event driven pipeline would allow us to reduce build times and increase efficiency on small tasks.

Knowing what I do now, I would still write our own pipeline, because there isn't an existing SSG that cuts it for what we need. I would just improve the way we did some of the things we did.