Scribd
Upload
34 views8 pages

FrontEnd Architecture

The document discusses three different FrontEnd architectures: Monolith, MicroFrontEnd, and Monorepo. Monolith combines frontEnd, backend, and database into one system, making maintenance challenging, while MicroFrontEnd breaks projects into smaller units, allowing for team independence but leading to code duplication. Monorepo consolidates multiple repositories into one, enabling library reuse and reduced code review time, but can suffer from poor performance and higher build times.

Uploaded by

kashinath Tilagul
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
34 views8 pages

FrontEnd Architecture

The document discusses three different FrontEnd architectures: Monolith, MicroFrontEnd, and Monorepo. Monolith combines frontEnd, backend, and database into one system, making maintenance challenging, while MicroFrontEnd breaks projects into smaller units, allowing for team independence but leading to code duplication. Monorepo consolidates multiple repositories into one, enabling library reuse and reduced code review time, but can suffer from poor performance and higher build times.

Uploaded by

kashinath Tilagul
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Lets learn

Different
FrontEnd
Architecture
today
Follow Vasanth Bhat on LinkedIn
Subscribe to uncommonGeeks
1. Monolith
Here frontEnd, Backend,
Database all together
considered as one system.
Code changes, deployment
all are made for one big
system.
As you can see on the left
hand side. For the entire
shop management, there
is just one team.

Follow Vasanth Bhat on LinkedIn


Subscribe to uncommonGeeks
Disadvantages Monolith

In monolithic architecture,
applications have huge components
and complex logic. Therefore,
maintaining or upgrading such
applications is challenging. Moreover,
integrating a new team can be a
difficult task.

Follow Vasanth Bhat on LinkedIn


Subscribe to uncommonGeeks
2. MicroFrontEnd

In very simple words, micro-frontEnd is an


architecture that divides Big project into small and
meaningful units. Which has their own frontEnd and
backend

Follow Vasanth Bhat on LinkedIn


Subscribe to uncommonGeeks
Advantages of MicroFrontEnd
1. Technology Agnostic.
2. Isolate Team Code.
3. Freedom to build and deploy independent
of other teams.

Disadvantages of MicroFrontEnd
1. Code duplication.
2. Same fix needs to happen on different
projects
3. Duplicate code review work.

Follow Vasanth Bhat on LinkedIn


Subscribe to uncommonGeeks
3. Monorepo
Instead of managing multiple
repositories, you keep all
your isolated code parts
inside one repository

Monorepo has nothing in


common with monolithic
apps. You can keep many
kinds of logical apps inside
one repo; for example, a
website and its iOS app.

Follow Vasanth Bhat on LinkedIn


Subscribe to uncommonGeeks
Advantages of MicroFrontEnd
1. Reuse of libraries.
2. Reduced code review time.
3. Combines advantages of micro-frontEnd as
each team owns its own part inside a
repository.

Dis-advantages of MicroFrontEnd
1. Poor Git performance when working on
large-scale projects.
2. Higher build time.
3. Sometimes unnecessary code will be
shipped with the product.
Follow Vasanth Bhat on LinkedIn
Subscribe to uncommonGeeks
Subscribe to
uncommonGeeks
Youtube channel
Follow VASANTH BHAT on LinkedIn

I will help you to clear your FrontEnd Interview

Subscribe to Uncommon Geeks Youtube Channel

You might also like