How anwesha-exavalu/slide-frontend works
Project type and purpose
• underwriterportal is a React-based single-page application (SPA) that serves as an insurance underwriter portal UI.
• It provides a rich client interface (forms, dashboards, charts, document viewers) to interact with underwriting APIs, authenticate users, view portfolios, create submissions, and track audit history.
File structure
• Top-level “frontend” directory holds the entire React app.
• “public” contains static HTML and assets.
• “src” is organized into:
• approutes (client routing)
• components (reusable UI widgets: form controls, tables, charts, modals, navbar, sidebar)
• constants (API endpoints, routes, theme config)
• context (React Context providers for loader, metadata)
• layout (page wrappers, headers, sidebars)
• pages (feature pages: Dashboard, Login, ForgotPassword, etc.)
• styles (SCSS/JSON style maps for components & pages)
README
• The README only lists the project name “underwriterportal” with no further architecture notes. We infer that this SPA calls a set of RESTful underwriting APIs, uses an auth service, and is hosted as static files.
Main components
a. Presentation Layer (React SPA)
• Browser / User Agent
• Static hosting (e.g., S3 + CloudFront or any CDN)
• React entrypoint (index.html + index.js)
• Client routing (React Router)
b. Authentication Service
• OAuth/OpenID provider (e.g., AWS Cognito, Auth0)
c. API Layer
• API Gateway / Load Balancer
• Underwriting microservices (submissions, document management, portfolio insights, audit service)
• Reporting/Analytics service
d. Data Layer
• Relational database (e.g., PostgreSQL) for policies, users, audit trails
• Object storage (e.g., S3) for documents
e. External services
• Email/SMS notification service
• Mapping service (for GeoMap component)
• Third-party risk/quote engines
Relationships & interactions
• User → CDN (loads SPA)
• SPA → Auth Service (login, token refresh)
• SPA (with auth token) → API Gateway → various microservices
• Microservices → Data Layer (DB, object store)
• Microservices → External services (email, mapping, quote engine)
• Audit events → Audit DB or event stream
Architectural patterns & design principles
• Client-server (SPA front-end + RESTful backend)
• Microservices (separate services for submissions, documents, reporting)
• Shared libraries vs. feature modules in front-end (components folder)
• React Context for cross-cutting concerns (loader, metadata)
• Static hosting & CDN for scalability
Relevant technologies & frameworks
• Frontend: React, React Router, Context API, SASS (main.scss), Chart libraries
• Hosting: S3/CloudFront (or Netlify/Vercel)
• Auth: OAuth/OpenID (AWS Cognito or similar)
• Backend: API Gateway, microservices (Node.js, Spring Boot, etc.)
• Data: PostgreSQL (policies, users), S3 (documents)
• External: SES/SNS or SendGrid (email/SMS), Mapbox/Leaflet
Capturing essential elements
• Don’t forget authentication and authorization flows.
• Both static asset hosting and dynamic data calls.
• Caching layer (e.g., CDN, Redis) if used.
• Error handling or fallback routes if significant.