NoSQL vs SQL ... when to use which?

🔥 UNCLESTEF'S DEVELOPER BOOTCAMP AND MENTORING PROGRAM

🔥 CODER'S CAREER PATHS WEBINAR - FREE 29 MINUTE VIDEO:

🔥 LIZARD WIZARD KOMODO - TRANSFORMATIONAL MIND TRAINING:

*************

WEB HOST PAYS FOR YOUR WEB DESIGN TRAINING IN 2021:

POPULAR & EASY CODING COURSES:

*************

🦎 Lizard Wizard Course:

📚 BOOKS TO READ:
… Complements Studioweb courses on HTML5, CSS3 and JavaScript.

The Naked Ape:

✉️ STAY IN CONTACT:
Stef's social links:

Stef's business channel:

👉 GOOGLE REVIEW:
Leave a Google review about Stef.

MY MOUSE & KEYBOARD:

SUPPLEMENTS THAT WORK AMAZING FOR ME:

Protein Essentials Beef Gelatine Powder:

... Healed my very bad knee. If you have joint problems, this *could do miracles for you.

Webber Naturals 88862 Glucosamine Chondroitin

MY CAMERA GEAR:
Canon EOS C70 Cinema Camera

Thanks!

Stef

#mentoring #codecourses #unclestef #codingcoach

[ead]

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.

[manueljarrin]

Favorite time of the day to hear from the tech uncle I never had!

[neomangeo]

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.

[davidchino]

Could you please explain the main steps to build an e-commerce main process and the people involved
Thanks

[notreallysure]

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.

[securethebag]

audio is trash. is the microphone a decoration?

[yalcinozer]

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.

[-Engineering-]

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.