Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Adding a cache layer to keep using the wrong database is an architecture failure - if you use Postgres from the get go you will not need the cache until way way later on anyway. (Side note, I’m team MySql but the same point applies)


What exactly is wrong about a solution that perfectly fits the most common use case out there, at a fraction of the cost/complexity?




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: