{ Simple Frontend }

Organize and split your frontend applications

As your organization and product grows, you will need to decide how to organize your frontend applications. You probably even have large applications that you need to maintain. I've beenadvocating for a monorepository setupfor a while now. However this is not a one-size-fits-all solution and even with a monorepository approach, you still need to decide how to organize your applications.

I designed this small questionnaire to guide through the process and make an informed decision:

What is your primary goal?
As the number of your applications grow, this is a growing pain that most companies want to address.
The most common use case for this setup is compliance reasons for example to adhere to Payment Card Industry Data Security Standard (PCI DSS) where you need stronger governance and audit trails.
How do you currently serve or plan to serve and split your applications?
For example https://website-home.com and https://website-blog.com
For example https://website.com/home and https://website.com/blog. This is often referred as microfrontends vertical split.
Do you want to share runtime dependencies between your applications?
You can still share regular packaged dependencies between applications. This is the most common setup.
Runtime dependencies allow to release hotfixes and features to your dependencies without having to synchronize and redeploy all your applications. This is often referred as microfrontends horizontal split.
;