Skip to content

MCP migration: hybrid dedup tuning (SQLite + Airtable) #11

@Mayank-glitch-cpu

Description

@Mayank-glitch-cpu

Tracking tradeoff from agentic MCP migration plan.

Decision: Use hybrid dedup — check local SQLite cache at ~/.jobsync/cache.db first, fall back to airtable_list_recent_jobs on miss, repopulate cache.

Open questions:

  • Cache TTL (24h? 7d?) before forcing an Airtable re-check
  • URL normalization strategy (strip query params? canonicalize per-ATS?)
  • Collision handling when two companies post the same role URL pattern
  • Reconciliation cadence: on every run vs periodic sweep

Context: Pure SQLite is fast but can drift from Airtable truth. Pure Airtable round-trips hit rate limits. Hybrid is the compromise but needs tuning.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions