3 ms·
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
by maccard 3mo ago
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)
- rafabulsing 3mo agoWhat exactly is wrong about a solution that perfectly fits the most common use case out there, at a fraction of the cost/complexity?