JPA
JPA Annotations
@Entity
@Table(name = "products")
public class Product {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
@Column(nullable = false, length = 100)
private String name;
@ManyToOne
@JoinColumn(name = "category_id")
private Category category;
@OneToMany(mappedBy = "product", cascade = CascadeType.ALL)
private List<Review> reviews;
}
JPA vs Hibernate
| Aspect | JPA | Hibernate |
|---|---|---|
| Type | Specification | Implementation |
| Annotations | Standard | Standard + proprietary |
JPA Best Practices
Entity Design
- Use @Column for constraints
- Implement equals/hashCode properly
- Use @Version for optimistic locking
- Map relationships correctly
Query Optimization
- Use JPQL over Criteria
- Implement pagination
- Use @Query for complex queries
- Avoid N+1 problems
Performance
- Use batch fetching
- Implement second-level cache
- Use read-only transactions
- Optimize lazy loading
Key Points
- Understanding JPA is essential for production systems
- Always consider scalability and maintainability
- Test thoroughly before deploying to production
- Monitor performance and set up alerting
Common Patterns
- Validation: Always validate input at the boundary
- Error Handling: Use structured error responses
- Logging: Log key events for debugging
- Testing: Unit, integration, and load tests
- Documentation: Keep docs updated with code changes
Practice Problems
Design and implement a solution for JPA in a backend system. Consider scalability, error handling, and production readiness.
Solution
// JPA implementation
// Key aspects: validation, error handling, logging, testing
public class JPA {
// Production-ready implementation
} Identify and handle edge cases for JPA. What happens under high load, with invalid input, or during failures?
Solution
// Edge case handling:
// 1. Null/empty input -> validation
// 2. High load -> rate limiting, queuing
// 3. Failures -> retries, circuit breaker
// 4. Concurrent access -> locks, idempotency Write a testing strategy for JPA. Include unit tests, integration tests, and performance tests.
Solution
// Test plan:
// - Unit: 80% coverage target
// - Integration: API contracts
// - Performance: latency, throughput
// - Chaos: failure injection Quiz
1. What is JPA?
2. @GeneratedValue purpose?
3. What is a common mistake when implementing JPA?
Flashcards
Question
What is JPA?
Click to reveal answer
Answer
Java Persistence API - ORM specification
Question
@GeneratedValue?
Click to reveal answer
Answer
Auto-generate primary key
Question
JPA best practices
Click to reveal answer
Answer
Follow SOLID principles, write clean code, test thoroughly, document decisions, and monitor in production.
Revision Notes
Key Takeaways
- 1. JPA is standard ORM specification
- 2. Hibernate implements JPA
- 3. Key annotations: @Entity, @Table, @Id, @Column
Interview Tips
- • Know JPA annotations
- • Explain JPA vs Hibernate
Cheat Sheet
JPA
- Standard ORM specification
- @Entity, @Table, @Id, @Column
- @GeneratedValue: auto-generate keys