5 ms·
Assumption that only private consumers consume fashion, trends and "Pepsi generations" is wrong. Corporate management, consulting and engineering subfields are
by nabla9 8y ago
Assumption that only private consumers consume fashion, trends and "Pepsi generations" is wrong.
Corporate management, consulting and engineering subfields are made of people
who don't check out from their personal needs when they work. Hype cycles, fashions, scenes and subcultures exist in software engineering just like they exist in corporate management and consulting. People want new and change.
SQL is the best for most database needs, but not for everything. It may seem boring if there is no marketing push that connects to emotions. SQL was established and boring for new software engineers. The emergence of "Web 2.0" in early 2000s started hype cycle for no-SQL. The 'scene' was so emotionally engaging that enterprises were abandoning SQL databases because "they don't scale" and because that's what their developers wanted to work with.
- ak39 8y agoYour analogy with fashion is useful, except it doesn't convey the wanton waste of money and time and brain cells this diversion took us through - we have come out poorer and it seems with significant loss of memory (intellectual and academic memory). Fashion choices are mostly innocuous ... this whole anti-SQL crusade was more akin to measles anti-vaccers who eventually forget the original controversies, somehow survive the ensuing epidemic only to one day stumble upon the very same measles vaccine they were against. They then present it to the infected leper colony as something new!
- lukaseder 8y agoI like this analogy given that the relational model solved all the problems of networked/hierarchical models, which preceded it. Yet, NoSQL aimed to regress towards pre-SQL times
- lugg 8y agoI'm curious about pre SQL database times. What sort of solutions were out there? What did the DBs look like before SQL was a thing? NoSQL fixes a lot of the mismatch with code models but imo doesn't really solve much else and lacks the expressive power of SQL when it comes to reporting software. I suspect most developers don't realise how much they are not the main user or consumer of SQL. (Business excel spreadsheets)
- collyw 8y agoKey value stores, Berkely-db was a popular one as I understand.
- nabla9 8y agoNavigational databases predated SQL databases (hierarchal or network/graph based). SQL was seen as huge improvement over navigational databases. Basically navigational database is just set of links to records. Filesystem can be treated as hierarchal database. DOM model is modern version of hierarchal model.
- jhayward 8y agoThe main model was CODASYL [1], a hierarchical navigational database standard. There were also various vendor-supplied things like IBM IMS for simple indexed storage/retrieval. [1] https://en.wikipedia.org/wiki/CODASYL https://en.wikipedia.org/wiki/CODASYL
- foobar_ 8y agoHonestly the only counter argument I can think of is stored procedures, which can get quite hairy. I would still say that stored procedures are still a better hell than ORM. The situation is so bad, I would actually like learn more about fashion and fabric than deal with another trend. Where is the objectivity ?
- collyw 8y agoI have recently joined a project where the database is mongodb. One thing That I have noticed is that its far more difficult to get a mental model of the application without a formal schema. In the same way that tests can act as a from of documentation, I now see that a database schema can act as a form of documentation as well. Something I haven't heard mentioned in any of the criticisms of no-sql. (The mid term plan is to move back to SQL for this project).
- nabla9 8y agoUsually the data and the model are more important and live longer (several decades) than the software itself. Traditionally you design the model for the data and interactions and then build the software around it. If you do fast prototyping this is not needed, you just need some quick and dirty persistence. Unfortunately the prototype is always the 1.0 version to ship.
- codetrotter 8y ago“Show me your flowcharts, and conceal your tables, and I shall continue to be mystified; show me your tables and I won’t usually need your flowcharts: they’ll be obvious.” —Fred Brooks, The Mythical Man Month