You're listening to coding blocks episode 124.

Subscribe to us and leave it to a review on iTunes, Spotify, Sich and more using your favorite

podcast app.

And check's out at coding blocks.net where you can find

show notes, examples, discussion, and a whole lot more. Send your feedback

questions and rants to comments at coding blocks net. Follow us on

Twitter at coding blocks or head to W. W. dot coding blocks and find all our social links

there at the top of the page.

With that, I'm Alan Underwood.

I'm Josac.

And I'm Michael Outlaw. This episode is sponsored by Data Dog.

The monitoring platform for cloud scale infrastructure and applications allowing you to see inside any stack, any app, at any scale, anywhere.

And Educative.io, level up your coding skills quickly and efficiently whether you're just

starting preparing for an interview or just looking to grow your skill set and

clubhouse the fast and enjoyable project management platform that

breaks down silos and brings teams together to ship value, not just features.

All right, and today we are continuing on with Chapter 2 of designing data intensive applications,

what we've been talking about for a while, and today we're going to be focusing in on talking

about the differences between document and

relational models. We kind of talked about this a little bit last episode, but we're going to

knock things out of the park this time. And in case you're following along with the book

we're actually starting with the section on

...