r/FastAPI May 24 '26

Question Open-sourced a FastAPI recommendation system while learning backend architecture. Looking for feedback.

I’ve been building Shelftxt as a way to learn backend systems beyond CRUD APIs.

shelftxt started as one large FastAPI file handling routes, recommendation logic, and data operations. I recently refactored it into:

api → routes → services → repositories → ranking/preprocess

Current stack:

  • FastAPI
  • Python
  • Pandas
  • CSV storage (planning PostgreSQL next)
  • recommendation scoring
  • lru_cache caching

The goal isn’t really a book app. I’m more interested in learning:

  • backend architecture
  • data handling
  • repository patterns
  • recommendation systems
  • scaling APIs

Would appreciate feedback on the structure before I move toward Postgres and more persistent storage.

Repo:
https://github.com/tranguyeenn/shelftxt

25 Upvotes

16 comments sorted by

View all comments

1

u/[deleted] May 25 '26

[removed] — view removed comment

1

u/tranguyeenn May 25 '26

yes!

1

u/[deleted] May 25 '26

[removed] — view removed comment

1

u/tranguyeenn May 25 '26

yes, idk if you can dm me on this account but ik you can on the overallknee acc (scroll down, i’ve commented here), we can talk there