with so many anti-sql blogs over the internet, am wondering if people are still using it as popularly as it was or has the dynamic shifted to noSQL
I am part of a project which uses PostGres. We are doing well. I am learning Mongo and Mongoose. And I find some of the syntax to fetch data a bit tricky. It is not as if Mongo or NoSQL does not have problems. You should see the kind of questions posted about Mongo in StackOverflow. Very tough to fix them unless you already know. I feel SQL is much easier compared to syntaxes in Mongo.
I believe RDBMS systems are very crucial for financial systems that need transaction heavy processing. So rather than discarding any db architechture, we all need to know all the benefits of them and make decision which to use by looking out the requirements of the application.
You often pick what you have the most in-house expertise in and build on top of that. I am comfortable with MongoDB, that's how I started out and that's my go to choice of DB even though I absolutely hate it. Over the last three years, I have to come to realize that, most data is relational and SQL should be the way to go to organize data, I am a huge fan of the discipline a SQL database can enforce and the sheer variety of operations it offers.
SQL is here to stay, for enterprise complex application is a must. If you know that your app will not exceed few thousand users at a time (like an ERP) it is better to use SQL.
SQL does not scale easily, you will have huge payments and at some point you will need to build very complex distributed databases architectures if you start to have millions users on-line.
I do have projects that uses SQL (PostgreSQL), all are for enterprises, I do not think to change that into the future. Using modern RESTful API's SQL can be used virtually anywhere.
This isn't even an argument. There are waaaaaayyyyyyy more working applications using SQL databases then there are NoSQL at this point in time. NoSQL is the next cool hip whizbang thing, but that doesn't make SQL "dead" by any chance. In fact, I'd say lets revisit this in 10 years, then we can talk. Actually, the more relevant question would be "Is NoSQL dead?" Given that it only holds between 5-20% of the market.
Tech news and marketing is cool, but theres a very real aspect of software where foundations do not frequently change. This is why algorithm, data structure, operating systems, and design pattern books from the 60-80s are still applicable today.
Those two will never "kill" each other. They're different tools. In some areas they overlap and one or another might "win", but in many areas they're completely different. More relations you need, closer it gets you to relational databases. And vice versa.
SQL is still a valid choice and in some cases preferable over noSQL and the other way a around.
The point is, it's a tool, if you need a screwdriver use a screwdriver, and if you need a hammer use a hammer.
And there are a lot of use cases where it doesn't matter at all so it boils down to taste and experience.
You can scale with both for example
very often just certain parts get moved to schemaless databases.
I even know a company that switched from Redis back to Memcached because the reads are much faster. It's all about what you need in the end.
SYED HASAN
ASP.NET, C#, Azure, SQL, SharePoint, HTML, CSS, Power Automate
Well. it depends on your architecture and also how you are distributing data over the network. If your system is distributed then go for NoSQL as it is much powerful while holding data and transmission. I am not saying SQL cannot. As I said if your data is distributed globally better go for NoSQL. As for examples: AirAsia, PIZZAHUT using Azure COSMOS DB which is NoSQL after all. This is my preference. I believe there are some who are much professional then me. I just shared my knowledge. :)