3 ms·
Fully agree. At that level, the justification for using MongoDB usually boils down to not wanting to deal with table schemas or SQL. In both cases, there are be
by vvillena 2y ago
Fully agree. At that level, the justification for using MongoDB usually boils down to not wanting to deal with table schemas or SQL. In both cases, there are better alternatives.
- formerly_proven 2y agoI’ve heard stuff like this from supposedly senior people - if we use mongo we can just store anything, we don’t need to think about a schema (also you can only store short strings in an SQL database)
- Vosporos 2y agoGood Lord the level of incompetence is terrifying
- stogot 2y agoMost people dontgain competence until they learn from their mistakes
- croes 2y agoRelated >Good programmers worry about data structures and their relationships https://news.ycombinator.com/item?id=41268803 https://news.ycombinator.com/item?id=41268803
- j45 2y agoIf we don’t think about it now we’ll really have to think about it way more later.
- markoman 2y agoHence, the birth of the dreaded 'technical debt'.
- hyper_cube 2y agoBut typically, if you do spend some time to think about schema, and relationships, you only have to spend a small amount of time, and map that into the appropriate place, and then usually you don't have to mess with it again. It's worth the investment.
- mrweasel 2y ago> not wanting to deal with table schemas or SQL. In most cases you're not even removing the concept of the schemas, your just moving them from your database to your application. Which in a sense is worse, especially if multiple applications needs to access the same database. As for SQL, I have yet to see something solve the problem for querying a database in a simpler manor.