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

I think the point is the problem isn't with the database, but with the code not cacheing results. This isn't some new problem. The database shouldn't be the problem because you should be cacheing results.


Cache is a not a solve-all solution. It is useful only for commonly used data, otherwise you just transfer the database problem to a caching problem.


If you squint, every database problem is a caching problem. The only reason we store the relations in their up-to-date form is that it's too expensive to continually replay the transaction log from the beginning of time.




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

Search: