Data Engineering

Storing, moving and serving data at scale.

2 subjects · 9 topics · 2 areas

Subjects covering this category

2 subjects

Subject · Beginner to Advanced
System Design
Turning a product's requirements into a first design for a web system, and knowing what each part is there for.
- Starting a Design
- The Parts of a System
- Moving Data Around
11 topics · 100 cardsnot started
Subject · Intermediate to Advanced
Spring Boot
Building a REST service with Spring Boot: wired to real data, validated, and fast enough to trust in production.
- Spring Boot Essentials
- Building REST APIs
- Data Access
12 topics · 77 cardsnot started

Databases

9 topics

Spring Boot
Spring Data JDBC vs JPA
Spring Data JDBC vs Spring Data JPA: persistence context, dirty checking, lazy loading, aggregates, and when to choose each.
Intermediate to Advanced7 cards · 4 qnot started
Spring Boot
The JPA Entity Lifecycle
The JPA entity lifecycle: the four states an entity can be in, the operations that move it, and when its SQL runs.
Advanced7 cards · 5 qnot started
Spring Boot
Transactions
Transactions with @Transactional: what it wraps, when it rolls back, why self-calls skip it, and REQUIRES_NEW.
Intermediate to Advanced7 cards · 4 qnot started
Spring Boot
Repositories with Spring Data
Spring Data repositories: CRUD without SQL, queries derived from method names, @Query, and what save() really does.
Intermediate to Advanced6 cards · 4 qnot started
System Design
API Pagination
API pagination with offsets and cursors: returning large results a page at a time without skipping rows or slowing down.
Beginner to Intermediate8 cards · 5 qnot started
System Design
Building Blocks of a Web System
The building blocks of a web system: DNS, CDNs, application servers and databases, and the path a request takes through them.
Beginner to Intermediate11 cards · 8 qnot started
System Design
Caching
Caching: keeping copies of frequent reads close, deciding when they go stale, and the ways a cache can take a system down.
Beginner to Advanced9 cards · 8 qnot started
System Design
Scaling Out
Scaling a web system up or out: bigger machines or more of them, what has to be stateless first, and what autoscaling cannot catch.
Beginner to Advanced9 cards · 5 qnot started
System Design
Architectural Styles
Software architectural styles: monoliths, layers, microservices, events and serverless, and the team and product each one fits.
Beginner to Advanced10 cards · 5 qnot started

Kafka

1 topic

System Design
Architectural Styles
Software architectural styles: monoliths, layers, microservices, events and serverless, and the team and product each one fits.
Beginner to Advanced10 cards · 5 qnot started