FastCharger — EV Discovery

The Problem

EV owners in high-density regions face fragmented station directories with slow spatial querying and outdated connector compatibility details.

Engineering Approach

Implemented a layered geospatial discovery architecture separating client discovery UI, high-performance Hono API routes, and a versioned station snapshot.

What I Built & My Contribution

Constructed discovery UI, station query filters, spatial indexing pipelines, rate-limiting middleware, and security headers.

Architecture & Data Pipeline

Next.js Map Client → Hono Geospatial API → PostgreSQL / PostGIS Spatial Index → Bundled Station Snapshot

System Architecture

[ User Location / Search ]
            │
            ▼
┌───────────────────────────────┐
│      Hono Discovery API       │
│   - Bounded Spatial Bounding  │
│   - Connector & Speed Filters │
└───────────────┬───────────────┘
                │
                ▼
┌───────────────────────────────┐
│   PostGIS Spatial Database    │
│   - ST_DWithin Geospatial     │
│   - Static Station Snapshot   │
└───────────────────────────────┘

Verified Outcomes & Metrics

Sub-50ms indexed spatial proximity queries; rate-limited discovery endpoints; strict zero-leakage security boundaries.

Verified Implementation

The inspected API mounts discovery and health routes with strict body limits, security headers, CORS boundaries, and rate limiting. Verification here represents code audit and local inspection, distinguishing functional code paths from external cloud provider accounts.

Boundaries & Known Limitations

A static station snapshot does not prove real-time charger stall availability or live hardware uptime. Live map tiles require third-party provider keys.