Artwork

Content provided by Freddy Guime and Bob Paulin. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Freddy Guime and Bob Paulin or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Episode 77. Sql or NoSql, To Normalize or to Not Normalize... that (STILL) is the question

41:19
 
Share
 

Manage episode 219521151 series 8374
Content provided by Freddy Guime and Bob Paulin. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Freddy Guime and Bob Paulin or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

So you may have thought about using NoSQL or a Document Database for taking care of you needs. But do you know why that might be not be a good (or a pretty bad idea?). Or you may have a Database that have been running fine, but it seems that you can't work with it anymore? (Is it time to move to NoSql? Would it help?).

We dive into the "Why" would you choose Databases vs NoSQL Data Stores, or when to ditch your MongoDB and actually come back to MySQL. In our current time of "WebScale" and "CloudReady" we get bombarded by choices! (Mongo, Dynamo, MariaDB, ElasticSearch) and while some of the offerings are great, it might not mean that is the Right choice for what we need to store.

So take a listen as we explore normalization and the strength and weaknesses of relational data vs unstructured data. We thank DataDogHQ for sponsoring this podcast episode

Don't forget to SUBSCRIBE to our cool NewsCast! Java Off Heap

Do you like the episodes? Want more? Help us out! Buy us a beer!

And Follow us! @javapubhouse and @fguime and @bobpaulin

  continue reading

108 episodes

Artwork
iconShare
 
Manage episode 219521151 series 8374
Content provided by Freddy Guime and Bob Paulin. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Freddy Guime and Bob Paulin or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

So you may have thought about using NoSQL or a Document Database for taking care of you needs. But do you know why that might be not be a good (or a pretty bad idea?). Or you may have a Database that have been running fine, but it seems that you can't work with it anymore? (Is it time to move to NoSql? Would it help?).

We dive into the "Why" would you choose Databases vs NoSQL Data Stores, or when to ditch your MongoDB and actually come back to MySQL. In our current time of "WebScale" and "CloudReady" we get bombarded by choices! (Mongo, Dynamo, MariaDB, ElasticSearch) and while some of the offerings are great, it might not mean that is the Right choice for what we need to store.

So take a listen as we explore normalization and the strength and weaknesses of relational data vs unstructured data. We thank DataDogHQ for sponsoring this podcast episode

Don't forget to SUBSCRIBE to our cool NewsCast! Java Off Heap

Do you like the episodes? Want more? Help us out! Buy us a beer!

And Follow us! @javapubhouse and @fguime and @bobpaulin

  continue reading

108 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide