Backend Study Lab · Games
← All games

Spring Data Boundary Clinic

Place Spring transactions, JPA fetch plans, rollback rules, and validated configuration at production boundaries.

Concept
Spring transaction and data boundaries
Difficulty
Advanced
Play time
9-11 minutes
Path
Spring Production

Interactive scenario

Playable game area: Make the next backend decision

Use the controls below. Feedback appears immediately and final scores stay in this browser.

Concept notes

Why this decision matters

Spring Data Boundary Clinic is focused practice for Spring transaction and data boundaries. It explains why each answer is safe, risky, or production-ready.

Keep Spring persistence behavior aligned with the business operation that must commit or roll back together.

Learning objectives

  • Own invariants in service transactions.
  • Fetch JPA data for the required response shape.
  • Make rollback and configuration behavior explicit.

How to play

  1. Inspect the service invariant and data access.
  2. Choose the smallest correct transaction and fetch boundary.
  3. Review rollback and startup behavior.

Scoring

  • Correct data-boundary decisions add 250 points.
  • Partial-state risks enter local review.
  • A perfect clinic scores 1,000.

Backend concept notes

A service transaction should match one application invariant rather than repository implementation details.

JPA performance requires explicit fetch shapes, query evidence, and production-dialect integration tests.

Common mistakes

  • Starting independent repository transactions.
  • Solving N plus one with a larger pool.
  • Assuming every exception rolls back identically.

Review misses from this game

Related Backend Study Lab tools

Use tools from the main site when you want to inspect real inputs.

Keep practicing nearby backend concepts while the mental model is fresh.

Databases Advanced

Query Plan Investigator

Investigate PostgreSQL query plans, cardinality gaps, scan choices, join amplification, and rollout evidence.

Time
9-12 minutes
Concept
SQL query planning and cardinality
  • Data & Performance
  • SQL Indexes
  • Performance
  • Databases
Play Query Plan Investigator
Databases Advanced

Transaction Isolation Arena

Defend database invariants from concurrent requests by choosing transactions, locks, constraints, snapshot reads, and optimistic concurrency.

Time
7-10 minutes
Concept
Database transactions, isolation anomalies, locks, and invariant protection
  • Data & Performance
  • Database Reliability
  • SQL
  • transactions
  • isolation
Play Transaction Isolation Arena

FAQ

Short answers for how this game fits backend interview and study practice.

Does @Transactional belong on every repository call?

No. Place it around the application operation whose writes and reads must form one consistency boundary.

Is eager loading the universal N plus one fix?

No. Use a fetch plan or projection tailored to the bounded use case and verify its SQL.

Leaderboard

Top 10 scores for the current ruleset. No account required.

Loading leaderboard...

    Finish the game to load your latest local score.