Back to marketplace

Section 12 Chapter 72 - Big Data

No description yet. This curated deck is ready for daily study.

Total cards: 13•Content version: v4•Public deck•Updated: 8/1/2026

Card preview (13)

#1
Front (Question)

Big Data

Back (Answer)

Data that won’t fit into the usual containers due to its volume, velocity or variety

#2
Front (Question)

Volume of Big Data

Back (Answer)

Too big to fit in a single server

#3
Front (Question)

Velocity of Big Data

Back (Answer)

Very short amount of time to respond

#4
Front (Question)

Variety of Big Data

Back (Answer)

Can be structured/unstructured

#5
Front (Question)

Why the lack of structure common in Big Data is a problem (2)

Back (Answer)

• Analysing it is difficult - Relational databases cannot be used as they require the data to be in a row-column format

#6
Front (Question)

How Big Data can be analysed

Back (Answer)

machine learning

#7
Front (Question)

Why the volume of Big Data is important

Back (Answer)

Relational databases don’t scale well across multiple machines

#8
Front (Question)

What programming paradigm is most suited to Big Data

Back (Answer)

Functional

#9
Front (Question)

How Big Data can be processed (with regards to volume)

Back (Answer)

Processing is distributed across multiple machines

#10
Front (Question)

Why functional programming is suited to Big Data (2)

Back (Answer)

• No side effects (Statelessness) • Higher order functions • Assignment is forbidden, which makes parallel programming much easier

#11
Front (Question)

Fact based model

Back (Answer)

An alternative to the relational data model. Immutable facts are recorded with timestamps rather than overwritten.

#12
Front (Question)

Graph Schema

Back (Answer)

Data is stored as nodes, properties and edges

#13
Front (Question)

Fact (In a fact based model)

Back (Answer)

A single piece of information