How mondrita/pharmasight works
Project type and purpose
• This is a full-stack web application (“Pharmasight”) for interactive sales data visualization in the pharmaceutical domain.
• The backend is a Spring Boot REST API with layered architecture (controllers → services → repositories) and Spring Security (JWT).
• The frontend is an Angular SPA that consumes the API, manages authentication, and renders tabular and map-based visualizations using OpenStreetMap.
File structure
• Top level:
• pharmasight-backend/pharmasight → Spring Boot project (build.gradle, src/main/java/... )
• pharmasight-frontend → Angular project (src/app/core, src/app/workspace, assets, environments, etc.)
• pharmasightDB.sql → initial schema for MySQL
• Backend layers:
• config (CorsConfig, SecurityConfig)
• filter (JwtFilter)
• controller (REST endpoints)
• service (business logic)
• repository (Spring Data JPA)
• model (JPA entities)
• dto (payloads)
• exceptions (error handling)
• Frontend modules:
• core/auth (login, JWT interceptor)
• core/layout (main container, routing)
• workspace/leaflet-map (map container, views, models, map routes)
• shared (guards, directives)
• services (auth.service, map.service, helper.service)
README for additional insights
• Live demo, prerequisites, setup steps
• Tech stack summary: Java11+, Spring Boot, Angular, MySQL, OpenStreetMap, Spring Security
• Key features: search with filters, table + map views, drill-down map interactions, market share & brand insights, Excel export
Elements
• Blue for frontend modules
• Green for backend layers
• Orange for external services
• Grey for database
• Rectangles for application components
• Clouds for external services