DegenFeed Architecture 🟢
DegenFeed is a protocol-agnostic social aggregator: one backend, many decentralized networks, one feed.
┌────────────┐ poll/webhook ┌───────────────────────┐
│ Farcaster │◀──────────────────▶│ │
│ Nostr │◀──────────────────▶│ Ingestion Layer │
│ Bluesky │◀──────────────────▶│ (one adapter per │
│ Lens │◀──────────────────▶│ protocol) │
│ ATProto │◀──────────────────▶│ │
└────────────┘ └───────────┬───────────┘
│ normalize
┌───────────▼───────────┐
│ Canonical Post Model │
│ author · body · refs │
│ network · ts · media │
└───────────┬───────────┘
│
┌──────────────────────────┼──────────────────────────┐
│ │ │
┌───────▼────────┐ ┌────────▼───────┐ ┌─────────▼───── ───┐
│ Postgres │ │ Redis │ │ Meilisearch │
│ (persistent) │ │ (feed cache, │ │ (full-text │
│ │ │ rate limits) │ │ search index) │
└────────────────┘ └────────────────┘ └──────────────────┘
Key design decisions
- Adapters own protocol weirdness. Each network adapter translates to the canonical model at ingestion; downstream code never sees raw protocol envelopes.
- Fan-in, not fan-out. Posts are stored once, referenced by many feeds.
- Cross-posting is first-class — a single author action can publish to multiple networks through the canonical model (see Cross-Posting).
- Search is an index, not the source of truth. Meilisearch can be rebuilt from Postgres at any time.
Failure modes
| Failure | Behavior |
|---|---|
| One network relay down | Adapter backs off; other networks keep flowing |
| Redis down | Feeds served from Postgres (slower, still correct) |
| Meilisearch down | Search disabled; feeds unaffected |