Why not to use NoSQL instead of RMDBS? (not Mongo)
-
I can't understand why would you like to be forced to create another table for relations if you can just use smth like references in most languages. What is the point of such complexity? I would rather type:
companies.First(cmpn=>cmpn.Name="Netflix").Employees.Avg(empl=>empl.Sal)
then use relations:
select * from companies join company_employess on ... join ... group by.. avg
I found some NoSQL DBs like Couchbase and other alternatives but all the companies demand SQL-devs. Why is it the way it is? (I'm using ASP.NET 6 + Blazor)
-
I can't understand why would you like to be forced to create another table for relations if you can just use smth like references in most languages. What is the point of such complexity? I would rather type:
companies.First(cmpn=>cmpn.Name="Netflix").Employees.Avg(empl=>empl.Sal)
then use relations:
select * from companies join company_employess on ... join ... group by.. avg
I found some NoSQL DBs like Couchbase and other alternatives but all the companies demand SQL-devs. Why is it the way it is? (I'm using ASP.NET 6 + Blazor)
Because you are not using the database you are using c# to do all your work. So only your application will work with the creation you call a database. Most of us (and I'm an old fart) know what a relational database is used for - storing data in a RELATED form and therefore any application can use the same relationships, reporting for instance. You need to do some research into the difference between a document database (NoSQl) and a traditional RMBDS. While there is a need and use for NoSql your example is not one of them EVERY company needs a RMDBS for this type of data.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
I can't understand why would you like to be forced to create another table for relations if you can just use smth like references in most languages. What is the point of such complexity? I would rather type:
companies.First(cmpn=>cmpn.Name="Netflix").Employees.Avg(empl=>empl.Sal)
then use relations:
select * from companies join company_employess on ... join ... group by.. avg
I found some NoSQL DBs like Couchbase and other alternatives but all the companies demand SQL-devs. Why is it the way it is? (I'm using ASP.NET 6 + Blazor)
Hopeless Idealist wrote:
I would rather type:...but all the companies demand SQL-devs.
First of course because companies do not operate to please you. They operate to make money. And that comes from pleasing customers. Both in sales and in follow up support. Additionally they must keep costs low. At the end of the day technologies do not drive company success. Rather it is matter of successfully creating a product(s)/service(s) which the company can maintain and enhance. And of course then selling it in the first place. Large companies almost always have multiple persisted datastores. And I only say 'almost' because I can't be sure that there is not one company out there that only uses one. I do know that Microsoft, Oracle, Netflix, Google and Amazon all use different ones.