CrudRepository in Spring Data JPA

Direct Answer

CrudRepository<T, ID> is Spring Data's basic repository interface for saving, finding, checking, counting, and deleting aggregates. Its exact return collection types and behavior come from the current Spring Data version. findById returns Optional<T>. save chooses new-entity persistence or merge through the store module; it is not a direct promise that every non-null id becomes one SQL UPDATE.

Code Example

// Spring Boot 3.2 + Java 17
@Entity
@Table(name = "customers")
public class Customer {
    @Id @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;
    private String name;
    private String email;
    // getters/setters
}

// No implementation needed — Spring generates it at runtime
public interface CustomerRepository extends CrudRepository<Customer, Long> { }

@Service
public class CustomerService {
    private final CustomerRepository repository;
    CustomerService(CustomerRepository r) { this.repository = r; }

    public Customer create(String name, String email) {
        var c = new Customer();
        c.setName(name);
        c.setEmail(email);
        return repository.save(c);            // INSERT (id was null)
    }

    public Optional<Customer> get(Long id) {
        return repository.findById(id);       // SELECT by PK -> Optional
    }

    public long total() {
        return repository.count();            // SELECT COUNT(*)
    }

    public void remove(Long id) {
        repository.deleteById(id);            // DELETE
    }
}

You wrote zero lines of SQL and zero implementation code — the injected CustomerRepository is a Spring-generated proxy.

Common Mistakes & Pitfalls

• Writing an Impl class — CustomerRepositoryImpl causes bean conflicts; Spring generates the implementation for you.
• Confusing it with JpaRepository — CrudRepository has no pagination/sorting or flush(); for those, extend JpaRepository.
• Wrong ID generic — CrudRepository<Customer, String> when @Id is Long fails at runtime; the second type parameter must match the id type.
• Expecting a List — findAll() returns Iterable<T>; convert it (e.g. with a loop or stream) or use JpaRepository for a List.
• Ignoring the Optional — findById() returns Optional<T>; calling .get() on an empty one throws NoSuchElementException.