Database and app orchestration in Spring Boot - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the role of Spring Boot in database and app orchestration?

Spring Boot simplifies app setup and orchestration by auto-configuring database connections, managing transactions, and integrating data access layers seamlessly.

beginner

What is a DataSource in Spring Boot?

A DataSource is a factory for connections to the physical database. Spring Boot auto-configures it to manage connection pooling and database access.

intermediate

How does Spring Boot manage transactions in database orchestration?

Spring Boot uses the @Transactional annotation to handle transactions, ensuring that database operations complete fully or roll back on errors, keeping data consistent.

intermediate

What is Spring Data JPA and how does it help in app orchestration?

Spring Data JPA provides easy integration with JPA-based databases, allowing developers to write less code for database operations and focus on business logic.

intermediate

Explain the concept of connection pooling in Spring Boot database orchestration.

Connection pooling keeps a set of open database connections ready to use, improving app performance by reusing connections instead of opening new ones each time.

Which annotation in Spring Boot is used to manage database transactions?

A @Service

B @Autowired

C @Component

D @Transactional

The @Transactional annotation tells Spring Boot to manage transactions for the annotated method or class.

What does Spring Boot auto-configure to manage database connections?

A Service

B DataSource

C Controller

D Repository

Spring Boot auto-configures a DataSource to handle database connections and pooling.

Spring Data JPA helps developers by:

A Writing SQL queries manually

B Managing UI components

C Simplifying database operations with less code

D Handling HTTP requests

Spring Data JPA reduces boilerplate code for database operations, letting developers focus on business logic.

What is the main benefit of connection pooling?

A Reusing open connections to improve performance

B Slower database access

C Increasing database size

D Encrypting data

Connection pooling improves performance by reusing existing database connections instead of opening new ones.

In Spring Boot, which layer typically interacts directly with the database?

A Repository

B Service

C View

D Controller

The Repository layer handles direct database access in Spring Boot applications.

Describe how Spring Boot orchestrates database connections and transactions in a simple app.

Think about how Spring Boot sets up and manages database access without much manual setup.

Explain the advantages of using Spring Data JPA in app and database orchestration.

Consider how Spring Data JPA helps developers write less code for database tasks.

Practice

1. What is the main role of a Spring Boot repository in database orchestration?

easy

A. To provide methods for saving, reading, updating, and deleting data

B. To define the database schema manually

C. To handle user interface rendering

D. To manage application security settings

Solution

1. Step 1: Understand repository purpose

   Spring Boot repositories act as a bridge between the app and the database, offering easy data operations.

2. Step 2: Identify repository capabilities

   They provide built-in methods like save(), findById(), delete(), which handle data safely without manual SQL.

3. Final Answer:

   To provide methods for saving, reading, updating, and deleting data -> Option A

4. Quick Check:

   Repository = Data operations [OK]

Hint: Repositories manage data actions like save and find [OK]

Common Mistakes:

• Confusing repositories with UI components
• Thinking repositories define database schema
• Assuming repositories handle security

2. Which of the following is the correct way to declare a Spring Data JPA repository interface for an entity User with primary key type Long?

easy

A. public interface UserRepository extends Repository<User> {}

B. public interface UserRepository extends JpaRepository {}

C. public class UserRepository implements JpaRepository {}

D. public interface UserRepository extends CrudRepository {}

Solution

1. Step 1: Recall correct interface extension

   Spring Data JPA repositories extend JpaRepository to get full CRUD support.

2. Step 2: Check syntax correctness

   public interface UserRepository extends JpaRepository {} correctly extends JpaRepository with User entity and Long ID type; others misuse implements or wrong generics order.

3. Final Answer:

   public interface UserRepository extends JpaRepository {} -> Option B

4. Quick Check:

   JpaRepository syntax [OK]

Hint: Use extends JpaRepository for repositories [OK]

Common Mistakes:

• Using implements instead of extends
• Swapping generic type order
• Extending incomplete Repository interface

3. Given the following Spring Boot repository method call:

Optional<User> user = userRepository.findById(5L);

What will user.isPresent() return if no user with ID 5 exists in the database?

medium

A. true

B. Throws an exception

C. null

D. false

Solution

1. Step 1: Understand findById return type

   findById returns an Optional which is empty if no matching record is found.

2. Step 2: Check isPresent behavior

   isPresent() returns false when Optional is empty, meaning no user found.

3. Final Answer:

   false -> Option D

4. Quick Check:

   Optional empty means isPresent() = false [OK]

Hint: Optional.isPresent() false means no data found [OK]

Common Mistakes:

• Assuming isPresent() returns true always
• Expecting null instead of Optional
• Thinking it throws exception if not found

4. Consider this Spring Boot repository interface:

public interface ProductRepository extends JpaRepository {
    List<Product> findByName(String name);
}

Which of the following issues will cause a runtime error when calling findByName(null)?

medium

A. No error; it returns an empty list

B. Method signature is invalid and won't compile

C. Calling findByName with null returns all products

D. Passing null causes a NullPointerException in query generation

Solution

1. Step 1: Analyze null parameter in derived queries

   Spring Data JPA derived query methods accept null parameters and generate SQL like WHERE name = null, which matches no rows (since NULL = NULL is false).

2. Step 2: Confirm behavior

   No exception is thrown at runtime or compile time; it safely returns an empty list.

3. Final Answer:

   No error; it returns an empty list -> Option A

4. Quick Check:

   findByName(null) = empty list [OK]

Hint: Null args in derived queries return empty lists safely [OK]

Common Mistakes:

• Thinking null causes NullPointerException
• Believing signature won't compile
• Assuming null returns all products

5. You want to update a user's email in the database using Spring Boot. Which sequence correctly orchestrates this update using repository methods?

1. Retrieve user by ID
2. Change user's email
3. Save updated user back to database

Which code snippet correctly implements this?

hard

A. userRepository.save(new User(id, newEmail));

B. userRepository.updateEmailById(id, newEmail);

C. var user = userRepository.findById(id).orElseThrow(); user.setEmail(newEmail); userRepository.save(user);

D. userRepository.findById(id).getEmail(newEmail); userRepository.save();

Solution

1. Step 1: Retrieve user safely

   Use findById(id).orElseThrow() to get user or throw if missing.

2. Step 2: Modify user object

   Set new email on retrieved user object.

3. Step 3: Save updated user

   Call save(user) to persist changes back to database.

4. Final Answer:

   var user = userRepository.findById(id).orElseThrow(); user.setEmail(newEmail); userRepository.save(user); -> Option C

5. Quick Check:

   Retrieve, modify, save = update pattern [OK]

Hint: Retrieve entity, change fields, then save [OK]

Common Mistakes:

• Trying to save new object without ID
• Using non-existent updateEmailById method
• Calling getEmail() instead of setEmail()