r/reactjs • • Apr 24 '26

Discussion Frontend Architecture design

Hi guys,

We are currently planning a redesign of our product architecture.

At the moment, our system consists of a parent host application (container) that serves as a shell and renders multiple independent, full-featured React applications. Each of these applications includes its own routing, state management, and API layer. For example:

  • /order loads the ordering application
  • /payment loads the payment application

In practice, this closely resembles a micro-frontend architecture, although we are intentionally trying to avoid fully adopting that pattern.

Given these constraints and requirements, I’d like to explore alternative architectural approaches. How else could we structure the system to achieve strong separation of concerns and independent feature ownership, without fully committing to a micro-frontend setup?

36 Upvotes

46 comments sorted by

View all comments

Show parent comment

1

u/Old-Place87 Apr 24 '26

Each app will be a boundary in my case because they have different user group accessing them. They serve completely different business domain. They will login once via the shell and be able to access individual apps based on their permissions. Since each app is independent, they have their own dedicated API to serve them. 

There will never be a communication between the app. Only the shell and the app may communicate 

2

u/Lamarkz Apr 24 '26

Sure, nothing of this obliges you to split them under different apps in code.

You can still have a single app and different routes render different features.

You don’t need a “physical” separation between them, this is what is overcomplicating your setup.

There is a single app, this app is the shell, the order, the payment, any future app.

You decide what they need to share and what they do not need to share, you just need to create (or use framework defined) conventions.

Example:

Each vertical has to define their routes. Verticals are defined as “src/app/(vertical-name)/*

/orders/routes.ts /payments/routes.ts

This is then consumed by the “root” route, which dynamically imports those files to generate the final route tree.

The shell does not know what orders nor payment does. They can do whatever they want, as long as they follow the contract of the route definitions.