Navigating Unstructured Data - Availability vs Analytics in NoSQL

on YouTube ↗27m

" summary

Argues that no single database handles batch, real time and huge variety at scale so architectures combine tools like Cassandra, Kafka, HDFS, Elasticsearch, Mongo and Redis for different roles. Recommends storing raw immutable events, using AP systems for availability, resolving conflicts with vector clocks / dotted version vectors, and partitioning via consistent hashing to avoid master failures. Claims this yields linear scalability and replayable streams but forces tradeoffs around latency, conflict resolution and eventual consistency.

AI-written summary · about

" chapters (7)

1. 0:00The Rise of Unstructured Data
2. 4:24NoSQL Database Fundamentals
3. 8:55Understanding the CAP Theorem
4. 13:11Partitioning and Scalability
5. 16:15Designing for Data Persistence
6. 20:11Modern Data Architectures
7. 26:01Summary of Challenges

" related talks

• 34mData Storage: NoSQL Toasters and a Cloud of Kitchen SinksCasey Rosenthal · RailsConf 2013
• 42mContemporary Approaches to Data at ScaleBen Stopford · Code Mesh 2015
• 57mMulti Tenant NoSQL and NewSQL Cloud data Design Patterns Deep diveRohit Bhardwaj · Great International Developer Summit 2023
• 01h 01mNoSQL: An AnalysisAndrew J. Brust · PASS Business Analytics Conference 2013
• 47mWhat's Ahead for Big Data?Dean Wampler · Code Mesh 2013
• 45mSay YES! to NoSQL: A Guide on When to Ditch Relational DatabasesAdrienne Braganza Tacke · NDC Sydney 2020
• 42mSay YES! to NoSQL: A Guide on When to Ditch Relational DatabasesAdrienne Braganza Tacke · AzConf 2020
• 45m50 Shades of Data: How, When, Why—Big, Relational, NoSQL, Elastic, Graph, EventLucas Jellema · Oracle Code One 2018