61 minutes
Imagine sitting down at a restaurant. Your food is already on the table, and the waiter hands you a menu of different dishes and silverware you can use to consume your meal. That’s a completely backwards experience, but it’s kind of how data architecture works today. We have our data in cheap storage, and then we purchase software that helps us consume it. Is this also wrong?
In this special episode, Tim and Juan are joined by Chad Sanderson, Head of Product, Data Platform at Convoy, to discuss whether we’re incorrectly architecting our modern data stack.
Lessons learned from Amazon and Facebook on building services before data
How to align your data team with business goals
Getting data architecture right often requires paying down legacy debt. What’s something you recently purchased that you maybe shouldn't have?
When you build on top of the swamp, it sinks.
Data consumer will always have a gap between the question that they are asking and what came from the source system.
“Knowledge layer or descriptive layer” - as close a representation of the real world as possible.
Special guests
Chad Sanderson
Head of Data Product, Convoy