Micro-frontend Architechture. Part 1.
Hello everyone! 🌟 This is the first part of the previously announced series of posts about an application with a micro-frontend architecture. Not everyone will have the same needs, but I hope everyone will find interesting information 📚.
So, let’s get started. We’ll be talking about the architecture of the front-end part of a CRM system.
What is a CRM? 🤔
CRM functions as a centralized task dispatcher for our agents in our company. Imagine a high-tech office assistant that distributes tasks among employees. When an agent logs into the system, this assistant starts directing tasks to them — calls from clients, chat questions, or tasks to call potential clients. Thus, the agent always knows what to do and can focus on interacting with clients instead of searching for what to start with. CRM here is a smart tool that helps efficiently organize customer service, ensuring every query is heard, and every need is met 🎯.
Main application requirements 🔍
I won’t delve into functional and non-functional requirements in detail but will highlight those that significantly affect the high-level architecture of the application:
- Scalability and long-term development. The application should be designed to easily adapt to changes in…
