Skip to content
Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations cover art

All Episodes

Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations — 183 episodes · page 1 of 2

#
Title
1

How Database Schema Evolution Shapes Tech Strategy

2

The Silent Killer Of Database Performance

3

How Database Latency Costs Companies Millions

4

Why Your Database Is Leaking Data Through Silent Failures

5

How Database Schema Drift Erodes Engineering Velocity

6

How Data Lineage Prevents Compliance Nightmares

7

How Database Indexes Drift And Cost You Money

8

How Database Indexes Actually Speed Up Queries

9

Why Your Database Is Leaking Money on Unused Indexes

10

Why Your Database Queries Are Slow

11

Why Your Database Sucks at Real Time Data

12

How Data Mesh Decentralizes Enterprise Tech

13

How Data Contracts Prevent Broken Pipelines

14

Why Your Database Chokes on Simple Queries

15

Why Your Database Is Wasting Money on Indexes

16

How Database Partitioning Saves Engineering Teams

17

The Hidden Cost of Data Modeling Mistakes

18

How Vector Databases Are Changing Search

19

How Database Caching Breaks Consistency

20

The Hidden Cost of Database Storage Efficiency

21

The Cost of Waiting for Database Consistency

22

The Real Cost of Database Vendor Lock-In

23

Why Your Database Chokes on Simple Queries

24

How Data Gravity Shifts Cloud Economics

25

How Data Normalization Prevents Billion-Dollar Glitches

26

How Database Locks Kill Your App Speed

27

The Hidden Cost of Database Consistency Models

28

How Database Sharding Scales Without Breaking

29

How Databases Handle Data Decay and Retention

30

How Database Schema Evolution Saves Engineering Teams

31

How Data Lineage Transforms Audit Compliance

32

How Database Connection Pools Save Systems

33

How Distributed Databases Handle Consistency Without Killing Speed

34

How Databases Handle Data Decay and Retention

35

How Database Caching Transforms App Speed

36

How Databases Handle the Midnight Traffic Spike

37

Why Your Database Is Slow Despite Perfect Indexes

38

How Database Partitioning Saves Cloud Costs

39

How Database Indexes Create Write Amplification Problems

40

The Silent Killer of Database Performance

41

How Database Indexes Create Write Amplification Problems

42

How Database Partitioning Saves Billions in Cloud Costs

43

How Database Column Stores Crushed Row Storage

44

How Database Row Formats Save Cloud Costs

45

How Database Partitioning Saves Billions in Cloud Costs

46

Why Database Indexes Create Write Amplification Problems

47

How Database Partitioning Saves Billions in Cloud Costs

48

Why Database Query Optimizers Underestimate Joins

49

Why Database Compaction Can Stall Under Write Load

50

Why Database Query Planning Uses Cost Models

51

Why Database Sharding Needs a Routing Layer

52

Why Database Transactions Use Two-Phase Locking

53

How Database Replication Lags Under Partitioning

54

Why Database Query Planning Uses Cost Models

55

Why Database Connection Timeouts Need Jitter

56

Why Database Backups Need Incremental Strategy

57

Why Database Caching Layers Need Write-Through Strategies

58

Why Database Snapshot Isolation Is Not Serializable

59

Why Database Storage Engines Use LSM Trees

60

Why Database WAL Is the Unsung Hero of Durability

61

Why Database Time Series Storage Uses Chunked Archives

62

Why Database Migrations Need Expansion and Contraction

63

Why Database Vectors Need HNSW Indexes

64

Why Database Connections Need Multiplexing Not Pools

65

Why Database Time Series Compression Uses Delta and Gorilla Encoding

66

Why Database Query Caches Fail Under Write Workloads

67

Why Database Denormalization Can Beat Joins for Hot Paths

68

Why Database Triggers Can Cause More Harm Than Good

69

Why Database Connection Pooling Breaks Under Burst Load

70

Why Database Indexes Use Adaptive Radix Trees

71

Why Database Statistics Need Histograms for Query Plans

72

Why Database Query Plans Go Wrong Without Histograms

73

Database Indexing with Sparse Indexes and B-Trees

74

Why Database Sharding Needs a Consistent Hash Ring

75

Why False Positives in Database Bloom Filters Are Hidden Cost

76

Why Database MVCC Needs Visibility Rules Not Locks

77

Why Database Replication Lag Breaks Read-Your-Writes Consistency

78

Why Database Autoincrement Keys Fail at Global Scale

79

Why Database Compression Uses Dictionary Encoding Not Run-Length

80

Why Database Recovery Needs ARIES Protocol

81

Why Database Serializable Snapshot Isolation Prevents Write Skew

82

Why Database Upsert Needs Merge Not Separate Insert or Update

83

Why Database Caching Needs a Write-Through Strategy

84

Why Write-Ahead Logging Is Critical for Database Durability

85

Why Database Partition Pruning Cuts Query Time Dramatically

86

Why Database Merge Joins Beat Hash Joins for Sorted Data

87

Why SQL Window Functions Outperform Self-Joins

88

Why Time-Series Data Needs Downsampling Not Raw Storage

89

Why Database Schema Changes Need Online Migration Not Downtime

90

Why Database Bloom Filters Defeat Expensive Disk Seeks

91

Why Database Cursor Fetching Needs Pagination Not Streaming

92

Why Database Deadlocks Need Wait-Die and Wound-Wait Schemes

93

Why Database Hybrid Transactional-Analytical Processing Matters

94

Why Database Query Routing Needs Read-Write Splitting

95

Why Database Sharding Fails Without a Consistent Hash Ring

96

Why Database Connection Timeouts Need Adaptive Retry Logic

97

Why Database Change Data Capture Needs Exactly-Once Semantics

98

Why Database Replication Needs Quorum Not Just Async

99

Why Database Vector Indexes Need Hierarchical Navigable Small Worlds

100

Why Database Compression Needs Dictionary Encoding Not Just Run-Length