Yep NoSQL db like MongoDB can be great.... BUT... Only when you are absolutely sure that there will be no need for foreign relationships, you have large data sets, flexible schemas, and you need some extra speed. Generally, you will be wanting to go for an SQL db like PostgreSQL, MySQL or MSSQL. You will be safe then knowing that if you need any relationships between fields, you will be fine. You will still get great performance. Really NoSQL is more niche for specific usecases with requirements I mentioned above. Like a site where you have a crap ton of data that is straight up stored as a "document" think more along the lines of a flat file that sometimes has some fields and sometimes not (so no set shema), that has no foreign relationships to other data in other tables.
This is primarily true for small-to-midsize projects. But in large projects, a complex SQL database has problems as you scale, both in capacity demand and requiring multiple development teams - this is why so many have adopted microservices and NoSQL. Many relationships can be represented with NoSQL by de-normalizing data. You will be responsible for things like referential integrity, but again, you're doing this for performance and scale. As with most things in our industry, it's a tradeoff.
I had a great time using the MySQL workbench (locally) along with Prisma ORM and populating Planetscale thanks to Prisma and the Planetscale CLI. I thought I'd have to learn a lot of SQL to get it moving but that was all resolved thanks to Prisma. But yeah, it was a great experience setting up the server and connecting it to Planetscale via Prisma.
I am working as a software engineer since March 2020. I have always avoided using SQL. I dont know why but SQL syntax just looked irritating to me. I am not working on too complex data, so MongoDB is good enough. Also displaying data as JS object like documents make it easier to grasp the general idea :-) Besides every tech has pros and cons, in the aspect of developer thoughts, I believe people has different tastes.
I like SQL syntax it's very easy to read and understand unlike NoSQL especially when the query is complex, I don't know how people can understand easily a query that is defined in a JSON object that can contains a lot of inner objects and arrays
If you ever come to understand databases and SQL, you will greatly come to appreciate its power and stuff it can do that NoSQL could not ever do! Every tool has its place and its own proper purpose. Learn how all those tools work and then you'll be a much more diverse professional programmer!
@@ForbTree-js1yv I mostly describe myself as a software developer. Somehow I wrote here "engineer". But your question still doesn't make any sense. I just declared my thoughts above, that's all.
We can make all type of relationships in nosql as well and that technology is moore developer friendly than SQL is. Node + nosql is go to way for almost every situation for companies rather than big enterprise like banks etc, cuz they're dinosaurs they don't change their legacy stack very often. At the end they're all same, write data onto HDD.
Yep NoSQL db like MongoDB can be great.... BUT... Only when you are absolutely sure that there will be no need for foreign relationships, you have large data sets, flexible schemas, and you need some extra speed. Generally, you will be wanting to go for an SQL db like PostgreSQL, MySQL or MSSQL. You will be safe then knowing that if you need any relationships between fields, you will be fine. You will still get great performance.
Really NoSQL is more niche for specific usecases with requirements I mentioned above. Like a site where you have a crap ton of data that is straight up stored as a "document" think more along the lines of a flat file that sometimes has some fields and sometimes not (so no set shema), that has no foreign relationships to other data in other tables.
This is primarily true for small-to-midsize projects. But in large projects, a complex SQL database has problems as you scale, both in capacity demand and requiring multiple development teams - this is why so many have adopted microservices and NoSQL. Many relationships can be represented with NoSQL by de-normalizing data. You will be responsible for things like referential integrity, but again, you're doing this for performance and scale. As with most things in our industry, it's a tradeoff.
I had a great time using the MySQL workbench (locally) along with Prisma ORM and populating Planetscale thanks to Prisma and the Planetscale CLI. I thought I'd have to learn a lot of SQL to get it moving but that was all resolved thanks to Prisma.
But yeah, it was a great experience setting up the server and connecting it to Planetscale via Prisma.
Planetscale and supabase are awesome
Favorite time of the day to hear from the tech uncle I never had!
I find NoSQL harder to learn
right on time for me 😄
Could you please explain the main steps to build an e-commerce main process and the people involved
Thanks
summed up in 2 minutes, wow
I am working as a software engineer since March 2020. I have always avoided using SQL. I dont know why but SQL syntax just looked irritating to me. I am not working on too complex data, so MongoDB is good enough. Also displaying data as JS object like documents make it easier to grasp the general idea :-) Besides every tech has pros and cons, in the aspect of developer thoughts, I believe people has different tastes.
I like SQL syntax it's very easy to read and understand unlike NoSQL especially when the query is complex, I don't know how people can understand easily a query that is defined in a JSON object that can contains a lot of inner objects and arrays
If you ever come to understand databases and SQL, you will greatly come to appreciate its power and stuff it can do that NoSQL could not ever do!
Every tool has its place and its own proper purpose.
Learn how all those tools work and then you'll be a much more diverse professional programmer!
lmao and here i am struggling to understand nosql
are u sure ure a software engineer?.
@@ForbTree-js1yv I mostly describe myself as a software developer. Somehow I wrote here "engineer". But your question still doesn't make any sense. I just declared my thoughts above, that's all.
We can make all type of relationships in nosql as well and that technology is moore developer friendly than SQL is.
Node + nosql is go to way for almost every situation for companies rather than big enterprise like banks etc, cuz they're dinosaurs they don't change their legacy stack very often.
At the end they're all same, write data onto HDD.
audio is trash. is the microphone a decoration?
Say no to NoSQL?
Just say NO to NoSQL! - Nancy Reagan(probably)