Database Backend
topic on 2 shows · 3 statements across 2 episodes
the MAD Podcast 
the a16z Podcast
3 statements about Database Backend, every show
Hitchcock: Traditional database engineers rarely rewrite backends from scratch
“If you were to have come from a database background, you probably wouldn't say, yup, we'll rewrite the entire database backend.”
Hitchcock: Managing multiple specialized database backends degrades overall system performance
“And actually, if you're doing that, With three or four different database backends that can become incredibly complicated, The performance can degrade over time as well, or just be harder to reach because you're working with different platforms.”
Cockcroft: Microservices sharing a single database create fragile distributed monoliths
“And it turns out if you don't break apart your database backend, and you just create lots of services to talk to it, you've actually created what's called a distributed monolith, which has all the same fragility of the monolith, and you can't update things ind…”