They say never jump in an argument late... but here goes... There is a lot of people arguing in the positive for polyglot persistence. The arguments sound pre

They say never jump in an argument late... but here goes... There is a lot of people arguing in the positive for polyglot persistence. The arguments sound pretty appealing - hammer, nail, etc - on the face of it. But as you dig deeper into reality, you start to realize that polyglot persistence isn't always practically a great idea. The primary issue to me boils down to safety. This is your data, often the only thing of value in a company (outside the staff/team). Losing it is cannot happen. Taking it from there, we stumble across the deeper issue that all databases are extremely difficult to run. DBAs dont get paid $250k/year for nothing. These systems are complex, have deep and far reaching impacts, and often take years to master. Given that perspective, I think it then makes the decision to use a single database technology for all primary storage needs totally practical and in fact the only rational choice possible.