React architecture for a huge business application

Question

So we\'ve recently picked up React in our company as the front-end technology to build our huge business web application. By saying recently, I mean we don\'t have any previous

Answer 1

So this is just to share my experience working on an enterprise react application that is in production for years in several banks. yes, you heard me right. Now you can imagine how huge the application will be if it's related to fintech (I know it's not always the case). we have huge modules (70+) with a complex logic that pretty much handles a lot of the work that a bank needs. Modules are both isolated and re-useable. I am going to give an example of only one module so you can imagine the size of each module.

• Card Production Module

1. Bulk Card Generation
2. Bulk Card Export
3. Bulk Card Request
4. Card Operations
5. Card Operations Approvals
6. Card Printing
7. New Card Requests
8. Pin Generation
9. Pin Printing

This application is a product, not a project and as a product it is configurable. Even the UI is configurable. I have been working on this application as a full-stack developer. Since it's pretty old the state management library that we are using is flux. With state management, the development speed is a little slow but the tradeoffs are better with us not being worried about state management. By far the application has been able to handle huge changes and things which seemed unachievable. Stability has also been a key element throughout this period.

On the back-end, we have Restful services build using Dot Net which supports both MSSQL Server or Oracle depending on the client's needs/feasibility.