**

Monolithic to micro-frontend migration.

**

I have been indulging in micro-frontends these last few days and here is what I would share. Make sure you read through chronologically to get the gist of it.

Ecommerce and online transactions for businesses have recently mushroomed. In 2020 alone, there was a 16 - 19% increase in online retail sales' share of total retail sales (according to estimates in an UNCTAD report , 3 May).

So suppose you are starting out your ecommerce store, all you require is a small scale website and it will suffice your needs. You have very few orders and you require only a handful of staff members. This website consists of the front-end and a business logic part that handles all your functionality. i.e the backend.

With not so involving apps on your site, like about us, blog section, manageable cart checkouts etcetera , a monolithic architecture will most likely cut it for you.

Over time, the ecommerce site grows and becomes a multinational business, and you process very many orders at a go, you are recruiting staff members, you are stocking up on goods etc, you are maintaining the inventory etcetera - This means that you have to beef up your site (more sections, more content, bigger capacity databases etc). There has to be accuracy in database queries lest
it breaks your application, or give erring reports.

You can solve this baggage by considering migration from monolithic to a micro-frontend architecture.

**

Micro-frontends

**
Micro-frontends refer to a sub-division of a front-end application into multiple independent sections which are a part of a whole.

For the approximately 260 islands of Japan to be still considered part of this state they communicate with each other. Verily, the constructs of micro-frontends have to be in consistent communication with each other.