How do feed readers store their data?

Open
#109 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
mysql, sql
Domain
databases

Research direction

This is an exploratory discussion about storage approaches for feed readers, with no project file, test, or entry point named. Read the issue thread and the referenced River5 project first, then compare the described MySQL approach with other storage models; completion is not defined by the issue.

Written by the indexing model from the issue text.

Description

I've been working on a MySQL version of a RSS feed reader server app. Unlike River5, which stores all data in JSON files, this reader stores all data in a database, and accesses the data via queries.

In the last year, starting with Bingeworthy and then Feedbase, I've learned enough SQL, and have expert help when I need it. Not sure when or if I will release it. I wanted to understand the issues.

I find SQL is an awkward tool for accessing this kind of data. Which got me to wondering how other feed reader apps store their data. I'm supposed to be such an expert on this stuff, and I admit I don't know what they're doing. I wonder if some of them are using object databases.

Dominant language
HTML
Stars
134
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.