Quote Management System
A single frontend codebase serving multiple insurance product lines was becoming a bottleneck: teams working on different quote modules kept blocking each other's releases.
- Company
- Fyn Tune Solution Pvt Ltd
- Role
- Software Engineer (React.js)
- Period
- May 2023 – Oct 2024
What I actually owned.
Technology used.
| Frontend | React.jsTypeScriptTailwind CSS |
|---|---|
| Architecture | Micro-frontends |
| Integration | Multiple backend REST APIs |
How it fits together.
- Shell app
- Quote module A
- Quote module B
- Quote module C
- Shared REST API layer
- $ Shell app → Quote module A (independently deployed)
- $ Shell app → Quote module B (independently deployed)
- $ Shell app → Quote module C (independently deployed)
- $ Each module → Shared REST API layer
A shell app composes independently developed and deployed quote modules, so one product line can ship without waiting on another's release train.
Decisions & tradeoffs.
Multiple teams needed to develop and deploy quote modules independently without a shared release bottleneck.
Processing 50,000+ quotes a week meant frontend performance under real load was not optional.
Metrics that matter.
What actually went wrong, and how it got fixed.
Built a reusable validation layer so each module could express its own quote rules without duplicating form plumbing.
Code-split by module and lazy-loaded non-critical paths, then measured and improved load efficiency.
Other case studies.
Amber Car Rental
A car rental agency needed to move off manual, phone-and-spreadsheet bookings to a real-time online platform — built and run solo.
Ease of Doing Business — MMRDA
A government Ease-of-Doing-Business platform for the Mumbai Metropolitan Region Development Authority had a legacy React codebase and multiple departmental workflows to keep running while improving it.