SQL vs NoSQL Databases: How to Choose
SQL vs NoSQL explained by data shape and access pattern, with concrete examples for relational, document, key-value, wide-column and graph databases.
A central repository that stores large volumes of raw data in its original format until it is needed for analysis.
A data lake accepts structured data like database tables, semi-structured data like JSON logs, and unstructured data like images or documents, usually on inexpensive cloud object storage. Data is stored first and structured later, an approach sometimes called schema-on-read.
This flexibility is useful for data science and machine learning, where analysts may not know in advance which data will prove valuable. The risk is that, without governance, cataloguing, and quality controls, a data lake can become a data swamp that nobody trusts. A related architecture, the lakehouse, combines the low-cost storage of a lake with the management features and query performance of a data warehouse.
Datasets so large, fast-moving, or varied that traditional tools struggle to store and process them efficiently.
Data LakehouseA data architecture that combines the low-cost, flexible storage of a data lake with the structure and query performance of a data warehouse.
Data MeshAn approach to data architecture that gives business domains ownership of their own data, shared as products across the organization.
Data WarehouseA system that stores cleaned, structured data from many sources, optimized for reporting and business analysis.
ETLExtract, Transform, Load: a process that pulls data from sources, cleans and reshapes it, and loads it into a destination such as a data warehouse.
Object StorageA cloud storage method that keeps data as individual objects with metadata in a flat structure, suited to large amounts of unstructured files.
ZettabyteA unit of digital information equal to one sextillion (10 to the power of 21) bytes, or one billion terabytes.
SQL vs NoSQL explained by data shape and access pattern, with concrete examples for relational, document, key-value, wide-column and graph databases.
A plain-English guide to big data: what the 3 Vs mean, real examples, how big data is processed and a simple test for whether your data is actually big enough to matter.
A practical roadmap to become a data engineer: which skills to learn in order, the cloud certifications worth knowing, portfolio projects that prove you can build pipelines and common paths in.