Designing Data-Intensive Applications – Data Models: Relationships

While we continue to dig into Designing Data-Intensive Applications, we take a step back to discuss data models and relationships as Michael covers all of his bases, Allen has a survey answer just for him, and Joe really didn’t get his tip from Reddit.

This episode’s full show notes can be found at https://www.codingblocks.net/episode124, in case you’re reading this via your podcast player, where you can be a part of the conversation.

Sponsors

• Datadog.com/codingblocks – Sign up today for a free 14 day trial and get a free Datadog t-shirt after creating your first dashboard.
• Educative.io – Level up your coding skills, quickly and efficiently. Visit educative.io/codingblocks to get 10% off any course or annual subscription.
• Clubhouse – The fast and enjoyable project management platform that breaks down silos and brings teams together to ship value, not features. Sign up to get two additional free months of Clubhouse on any paid plan by visiting clubhouse.io/codingblocks.

Survey Says

Which keyboard do you use?

Take the survey at: https://www.codingblocks.net/episode124.

News

• Thank you for the awesome reviews:
  • iTunes: Kampfirez, Ameise776, JozacAlanOutlaw, skmetzger, Napalm684, Dingus the First
• Get your tickets now for NDC { London }, January 27th – 31st, where you can kick Allen in the shins where he will be giving his talk, Big Data Analytics in Near-Real-Time with Apache Kafka Streams. (ndc-london.com)
• Hurry and sign up for the South Florida Software Developers Conference 2020, February 29th, where Joe will be giving his talk, Streaming Architectures by Example. This is a great opportunity for you to try to kick him in the shins. (fladotnet.com)
• The CB guys will be at the 15th Annual Orlando Code Camp & Tech Conference, March 28th. Sign up for your chance to kick them all in the shins and grab some swag. (orlandocodecamp.com)

Relationships … It’s complicated

Normalization

• Relational databases are typically normalized.
  • A quick description of normalization would be associating meaningful data with a key and then relating data by keys rather than storing all of the data together.
• Normalization reduces redundancy and improve data integrity.
• Relational normalization has several benefits:
  • Consistent styling and spelling for meaningful values.
  • No ambiguity, even when text values are coincidentally the same, for example, Georgia the state vs Georgia the country.
  • Updating meaningful values is easy since there is only one spot to change.
  • Language localization support can be easier because you can associate different meaningful values with the same key for each supported language.
  • Search for hierarchical relationships can be easier, for example, gett