diff --git a/content/docs/why/jpa.md b/content/docs/why/jpa.md
index ecd50df..f5e7ebf 100644
--- a/content/docs/why/jpa.md
+++ b/content/docs/why/jpa.md
@@ -15,5 +15,54 @@ seo:
 ---
 
 
-Spring JDBC Template
+## Comparison with JPA (Java Persistence API)
+
+### 1. Query Handling
+- **JPA**: In JPA, the framework abstracts away the SQL queries by using JPQL (Java Persistence Query Language) or a Criteria API. This simplifies the developer's work by automating the generation of SQL queries, reducing the amount of boilerplate code.
+- **mysqlComponents**: In contrast, `mysqlComponents` directly uses Java's native libraries for query execution. Developers have full control over the SQL queries, which provides flexibility for complex or performance-critical queries. 
+
+### 2. Learning Curve
+- **JPA**: With its abstraction, JPA has a steeper learning curve due to the complexity of the framework, annotations, entity management, and the need to understand the JPA lifecycle.
+- **mysqlComponents**: Since it relies on Java’s native libraries and requires developers to write SQL directly, `mysqlComponents` is straightforward for those already familiar with SQL, resulting in a flatter learning curve.
+
+### 3. Control Over SQL
+- **JPA**: JPA generates SQL queries based on object mappings, which may not always be optimal or well-suited for complex queries. Custom queries are possible, but using native SQL within JPA breaks its abstraction and might complicate code maintenance.
+- **mysqlComponents**: Developers have complete control over the SQL syntax and logic, which can lead to more optimized and tailored queries.
+
+---
+
+## Advantages and Disadvantages of JPA
+
+### Advantages of JPA:
+1. **Abstraction**: Simplifies interaction with databases by abstracting the SQL layer, allowing developers to focus on the business logic.
+2. **Entity Management**: Automates the persistence lifecycle, including transactions, caching, and object-relational mapping (ORM), leading to less boilerplate code.
+3. **Cross-Database Support**: JPA is database-agnostic, making it easier to switch databases without rewriting queries.
+
+### Disadvantages of JPA:
+1. **Performance Overhead**: The abstraction adds a performance overhead, especially for complex queries. The generated SQL may not always be optimized.
+2. **Learning Complexity**: JPA requires a good understanding of ORM concepts, annotations, and persistence lifecycle, which increases the learning curve.
+3. **Lack of Flexibility**: Complex queries are harder to write and manage within the JPA framework. Sometimes, developers need to use native SQL, negating the benefit of the abstraction.
+
+---
+
+## Advantages and Disadvantages of `mysqlComponents`
+
+### Advantages of `mysqlComponents`:
+1. **Full SQL Control**: Developers write and execute native SQL queries directly, allowing for better performance and optimization for specific use cases.
+2. **Simplicity**: There’s no need to learn an ORM or abstraction layer, making the library easier for developers familiar with SQL and Java.
+3. **Lightweight**: No additional ORM overhead means better performance, especially for applications with complex query requirements.
+
+### Disadvantages of `mysqlComponents`:
+1. **Manual Query Management**: Since there’s no abstraction, developers must manage SQL queries, transactions, and entity mapping manually, increasing the potential for errors and requiring more effort.
+2. **Database-Specific**: SQL queries are specific to the database being used, which can limit cross-database portability unless developers account for different SQL dialects.
+3. **No Caching**: Unlike JPA, which provides caching mechanisms, `mysqlComponents` doesn’t handle caching natively, so developers must implement caching on their own if needed.
+
+---
+
+## Conclusion
+
+`mysqlComponents` is a robust alternative for developers who prefer fine-grained control over their SQL queries. While JPA is ideal for projects where abstraction and ease of use are critical, `mysqlComponents` excels in performance-sensitive applications where developers require full control over SQL execution.
+
+Each framework has its strengths and weaknesses, and choosing between JPA and `mysqlComponents` depends on the specific needs of your application, such as performance, complexity, and developer expertise.
+