4 ms·
Choose the right tool for the right job. We are all building unique systems solving unique problems. SQL is good for some things and NoSQL is good for some thi
by csneeky 10y ago
Choose the right tool for the right job. We are all building unique systems solving unique problems. SQL is good for some things and NoSQL is good for some things.
If you are taking the time and (someone else's) money to build something do it right and research how various data stores work up front. You should be at the point where it is obvious what the right decision is in your mind and if it isn't...get your learn on until it is.
- paulddraper 10y agoAnd the thesis of this article is that SQL is overwhelmingly the more versatile and better choice.
- csneeky 10y agoChoice for what? The article talks about a very specific domain (web applications solving a certain class of problem). Many organizations use multiple data stores and handle different problems. At Goldman Sachs there is almost every imaginable type of data store in use. All carefully vetted decisions that are largely the right choice much of the time. Almost all of it flows into some form of web application at some point in time in a giant interconnected system. I am very happy we don't use a single class of data store. If we did we'd be fucked. The "thesis" may apply very narrowly to a small web app of a certain size. But honestly if you are building something that cookie cutter are you really building something unique? What you are doing has probably been commoditized.