Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations

PODCAST · business

Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations

Lucas and Luna sit down at the database-engineering workstation to dissect the world of SQL, NoSQL, and data storage. Each episode takes a single data persistence technology—PostgreSQL, MongoDB, Redis, Cassandra—and walks through its architecture, trade-offs, and real-world deployment patterns. Lucas, with a journalist's precision, charts the evolution from relational schemas to document stores, while Luna presses on cost models, query latency, and the operational headaches of sharding. They avoid vendor cheerleading; instead, they weigh CAP theorem constraints, indexing strategies, and the messy reality of migration. The listener is a developer, data engineer, or technical founder who needs to decide where to put the bytes—and why. Expect no 'best database' declarations, only sharp conversations on consistency, availability, and partition tolerance as they play out in companies like Uber, Netflix, and GitHub. By the end of each episode, you'll understand not just what a database does,

No episodes available yet.

Type above to search every episode's transcript for a word or phrase. Matches are scoped to this podcast.

Searching…

We're indexing this podcast's transcripts for the first time — this can take a minute or two. We'll show results as soon as they're ready.

No matches for "" in this podcast's transcripts.

Showing of matches

No topics indexed yet for this podcast.

Loading reviews...

ABOUT THIS SHOW

Lucas and Luna sit down at the database-engineering workstation to dissect the world of SQL, NoSQL, and data storage. Each episode takes a single data persistence technology—PostgreSQL, MongoDB, Redis, Cassandra—and walks through its architecture, trade-offs, and real-world deployment patterns. Lucas, with a journalist's precision, charts the evolution from relational schemas to document stores, while Luna presses on cost models, query latency, and the operational headaches of sharding. They avoid vendor cheerleading; instead, they weigh CAP theorem constraints, indexing strategies, and the messy reality of migration. The listener is a developer, data engineer, or technical founder who needs to decide where to put the bytes—and why. Expect no 'best database' declarations, only sharp conversations on consistency, availability, and partition tolerance as they play out in companies like Uber, Netflix, and GitHub. By the end of each episode, you'll understand not just what a database does,

HOSTED BY

Fexingo

CATEGORIES

URL copied to clipboard!