Sites typically grow in size and complexity; over time, teams add new content and new sections. With the Jamstack architecture , sites are pre-built as static assets and hosted on a CDN. So as more content is added to the site, the build times can grow. This also depends on the kind of processing you do in the build phase (processing images takes a really long time), the static site generator you use to build the site and the infrastructure you build the site on. For the purpose of this article, I am going to focus on how to structure the site, and less on the specific frameworks and tools to build it.
Long Build times means that your editors and developers have to wait for some time before they can preview the changes they have made or go live with it.
Netlify not only provides the infrastructure and workflows for frontend teams to build and host sites really easily but also really clever features that allow your site to scale up. This blog post walks through a scalable way to architect the site while also using Netlify Redirects and Proxies to provide a uniform experience for the end users of your site.
As sites grow, the time and complexity required to build and maintain them grows as well. To keep your site builds fast, consider breaking your site into smaller, focused microsites, then using Netlify redirects/proxy to recombine them to provide a seamless web experience for your end users.
Building a large site on Netlify
- Marketing pages (about us, values, contact us etc) that are mostly static and barely change in content.
- Blog (a few 100 posts, keeps growing, content editors use the headless CMS to post content)
- Product catalogue and information (this is fed into the headless ecommerce platform)
When the site builds, the static site generator will use APIs to pull content and product information (images, descriptions, etc.) and build static assets for each of the content/code changes will trigger builds on Netlify. Folks will have to wait for the site to build before changes go live.
Splitting the large site into microsites
Instead, what if you split the site up into multiple smaller sites; one per section? In our e-commerce site example, the logical split seems to be the marketing pages, the blog and the product catalog. Maybe if you are selling several designer brands, each brand can be a microsite as well.
What does building a site this way look like?
Splitting up the site will reduce the build time
- The build time is much smaller now, corresponding only to the microsite that you are building at any time.
- Different teams can add content to the microsites independent of each other.
- Content updates to your site goes live much faster than before.
Setting up domains to reflect microsites
Now that we know how this architecture affects build time, let’s move on to Hosting. Here we have two options based on whether you want to use subdomains or different URL paths for the different sections of your site.
Set up the microsites as their own subdomains, use Netlify Redirects
- You have the main www subdomain for the landing page of the site.
- 1. say www.example.org.com
- Each microsite has a custom subdomain.
- 1. Each of the other sections are subdomains like blog.example.org.com, products.example.org.com.
- You can now host each of these subdomains on the Netlify High Performance Edge so that users see the content on the site as soon as possible and as reliably as possible.
- You redirect users from 1 subdomain to the other using Netlify Redirects.
Setting up the redirects is very straightforward on Netlify.
/blog /https://blog.example.org/:splat 301
/products /https://products.example.org/:splat 301
Setup the microsites as different URL paths, proxy content from them
If you do not want separate subdomains per section, you can still populate the Blog and Products section by proxying content from those microsites.
- You have the main www subdomain for the landing page of the site – same as above.
- The other microsites retain the default netlify subdomain say blog.netlify.app and, products.netlify.app
- You host the main www on our High Performance Edge network.
As users navigate to different paths in your site, say www.example.org.com/blog, the content from the blog microsite will be proxied to them.
By adding a single line of configuration to a
_redirects file or the
netlify.toml, we can catch all requests for URLs which can be satisfied by assets deployed to the Netlify High Performance Edge, and proxy all others through to other sites, either on or off Netify.
/blog https://blog.netlify.app/:splat 200
/products https://products.netlify.app/:splat 200
Considerations for splitting up a large site into smaller sections
It is totally up to you how you split the site, but some ways to think about it are:
- Are there parts of your site that change often via frequent edits, or new content being added often?
Are there parts of your site that are more static than the rest?
- Sometimes most of the site is static, while a section of it can be dynamic, making API calls and changing frequently.
Are there parts of your site that need to be LIVE much faster than others?
- If your site has a section (like Products or “breaking news”) that needs to go live soon without too much build time?
Are there different teams that contribute/own different parts of your site?
- If your site is really big, and several teams contribute to it (say Product, Marketing, Engineering etc), then it can make sense to split up the site by these functionalities.
I used an ecommerce application as an example, but this can easily extend to any kind of web property. Docs sites for instance grow in size, and different teams internally are responsible for the different products/services that a company offers. That will be a great candidate for this architecture. In fact, the Citrix docs site is built and hosted on Netlify, and they have 120 microsites in production.
Achieving Optimal Build Times!!
This way, you can split your site into microsites based on different criteria to achieve optimal build time. The end user browsing your site still gets a superior web experience on your site with the redirects and proxy rules that you set up per site.
Also, based on the type of site you are building, it might not even matter that the site takes a while to build.
- For instance, yours could be a mostly static site that barely changes in content or code, and that content does not have to go live immediately.
- Or you have a nightly build scheduled, and it does not matter how long the site takes to build.
If you and your team are working on a large site or have a use-case in mind for Netlify, drop us a line and we will get in touch with you.