╰☆☆ ɴᴏ, ɴᴏsǫʟ ɪsɴ'ᴛ ᴀ ᴍɪʀᴀᴄʟᴇ sᴏʟᴜᴛɪᴏɴ ☆☆╮ Although NoSQL solutions are interesting when used properly, it is clear that fewer and fewer people master the Relational Model and that this has serious consequences for the quality of solutions. NoSQL is just another tool in our toolbox, not a pauperization of what we can implement. There is no silver bullet.
No SQL solutions? Or NoSQL solutions?
I worked on an existing project (a huge one, it wouldn't have been funny, otherwise) using mongoDB to store data... The backend lead tried to duplicate data in a postgresql structured database, and to compare response time on several requests, between mongoDB and postgresql. It was awesome : postgresql was far faster than mogoDB (suprising... not). The product owner said switching database would be too expensive, so the project is still using mongoDB... and finding solutions for the software not to be too slow, go on being expensive all over the years...
Ed Hodapp
1w
Folks like to go from 0 to massive scale in one shot. I think that is always a mistake. Designs do not transfer to solutions for complex systems. You need to discover the way to solve your problem yourself. It is more important to follow the principles of continuous delivery and immediately fix any bad smells from that than to map someone else’s solution to their problem to yours. Get the dev environment and processes in place correctly, then leverage that to learn what you really need to know.
Python Back-end Developer
2wNever used NoSQL. But I like work with SQL There are less cases to use NoSQL then SQL I think