3 ms·
>For me as a not to DB savvy developer it was easy to start developing and administrating This point is repeatedly made about mongo, php and so on: to me it so
by JonnieCache 12y ago
>For me as a not to DB savvy developer it was easy to start developing and administrating
This point is repeatedly made about mongo, php and so on: to me it sounds like "This gun is so easy to use, it allows me to start spraying bullets around with no training and no knowledge of how it works!" or "This car is so simple I can go 150mph on the freeway the first time I got behind the wheel!"
Databases are massively powerful systems and they are used almost exclusively for business applications and matters of import. Why is "I can use it to make long-term consequential actions without any idea wtf I'm doing!" a plus point?
- lafar6502 12y agoIt's just a piece of software, a basic tool - not a war machine that requires 10 years of training, really no need to patronize. I'm really glad not only almighty Oracle admins can handle a database today
- mhd 12y agoRight, because we all know there's just a huge void between "put it in in some kind of form, we'll get it out somehow" an "let's tweak the undocumented redo log retention policy to eke out the necessary performance for our massively joined manifested view that mostly consist of analytical functions". It's "basic" as in your data being your foundation, not in rudimentary. And to be fair, most of the things that aim to replace SQL tend to be about as complicated. TANSTAAFL.
- lafar6502 12y agoYou could buy lifelong supply of free lunches for the price of enterprise licence of a well known SQL database.
- vkjv 12y agoBecause you can immediately switch your focus to things that add direct value your to your business.
- nemo44x 12y agoIt allows you to get started amazingly fast and has great client support. You don't have to think much about the DB side of things - just throw data into it. It's also where people get into trouble. After they've done this and built their MVP they don't go back and rethink their data decisions. Then scale issues occur, among other things. But it's also very easy to change your schema while iterating to serve your use cases better. But it's up to the users to change things and to learn which types of patterns scale better and to actually learn how to use the database to their advantage after gaining some experience. Learning how to model documents effectively is rather important.