hoangsonww/EstateWise-Chapel-Hill-Chatbot

Isochrone Provider Integration & Redis Caching

Open

#59 opened on Aug 13, 2025

View on GitHubContributor guide
 (4 comments) (0 reactions) (2 assignees)TypeScript (21 forks)auto 404
backendbugchoreci/cddocumentationenhancementfrontendgood first issuehelp wanted

Repository metrics

Stars
 (38 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary Generate travel-time polygons via a pluggable provider (Mapbox, OpenRouteService, Google) and cache by normalized request hash to meet latency goals.

Acceptance Criteria

  • POST /api/commute/isochrone returns GeoJSON polygon(s) for { destinations[], mode, window, minutes }.
  • Requests normalized and hashed; cached results returned when available.
  • P95 cached response ≤ 5s; cold path ≤ 10s on happy path.
  • Rate limiting and retry/backoff with exponential jitter.

Tasks

  • Provider abstraction + config flags
  • Request normalization + hashing
  • Redis get/set with TTL; metrics on hit ratio
  • Error mapping to user-friendly messages
  • Unit tests: hashing, caching, retries

Contributor guide

Research direction
Start by implementing the provider abstraction interface and request normalization. Then add Redis caching with TTL and metrics. Follow the acceptance criteria for performance and error handling.
Tech stack
typescriptnodejsredis
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65