How it-at-m/dave works
Project Overview
• DAVe is a full-stack application for commissioning, recording, and visualizing traffic counts.
• The project supports multiple portals (Data, Admin, Selfservice) that interface with one or more backend services.
• It leverages a modern stack including Java 21 with Spring Boot, ElasticSearch, PostgreSQL on the backend and Vue.js (with TypeScript, Vuetify, and Leaflet) on the frontend.
• There are clearly defined client interfaces and backend services with external systems (databases, search engines) that you need to include.
Main Components
a. Frontend Portals:
• Data Portal: Handles presentation and graphical representation of traffic counts.
• Admin Portal: Manages administrative tasks.
• Selfservice Portal: Provides user-side services.
(These might be represented as separate blocks or modules; note that each of these has a separate repository as mentioned in the README.)
b. Backend Service:
• The core service implemented in Java (Spring Boot based) which handles business logic, data processing, and REST API services.
c. External Systems:
• PostgreSQL: For relational data persistence.
• ElasticSearch: For high-performance searching and analyses.
d. Integration/Interfaces:
• A connection module/interface between the backend and external systems.
• Possibly a simple data pipeline or API interface for importing/exporting traffic count data.
Architectural Relationships & Interactions
• The Backend-Service interacts with PostgreSQL for transactional data and with ElasticSearch for indexing and search functionalities—show these interactions using direct connections.
• Internal data flows such as data received from portals being stored in the database, processed, and then made available for reporting or visualized charts.
• If applicable, note any integration points with internal services (such as EAI Reports, EAI GEO, and the still-under-construction EAI S3).
Final Recommendations
• Every component is clearly labeled with its name and role.
• Incorporate any architectural patterns visible (like separation of concerns between UI, logic, and data layers).