주제 비교 허브

JDBC vs JPA

JDBC 과 JPA 의 차이를 구조화된 비교 표에서 확인한 뒤, 관련 면접 질문, 퀴즈, 유사 비교로 이어가세요.

2 비교 포인트

3 관련 비교

차이점 비교

JDBC vs JPA - A key comparison and difference of the topics or subjects that will help you understand which is best for your use case. Check out to compare JPA and JDBC as very common job interview questions.

비교 개요

JDBC 과 JPA 의 차이

JDBC 이 나란히 비교의 첫 번째 주제입니다.

2 현재 이 페이지에서 확인할 수 있는 비교 항목입니다.

JPA 이 나란히 비교의 두 번째 주제입니다.

JDBC Interview Online Test	JPA Interview
JDBC is a standard for Database Access.	JPA is a standard for ORM.
JDBC is a standard for connecting to a DB directly and running SQL against it - e.g SELECT * FROM USERS, etc. Datasets can be returned which you can handle in your app, and you can do all the usual things like INSERTS, DELETES, run stored procedures, etc. It is one of the underlying technologies behind most java database access (including JPA providers). One of the issues with traditional JDBC apps is that you can often have some crappy code where lots of mapping between datasets and objects occur, logic is mixed in with SQL, etc.	JPA is a standard for Object Relational Mapping. This is a technology which allows you to map between objects in code and database tables. This can "hide" the SQL from the developer so that all they deal with are java classes, and the provider allows you to save them and load them magically. Mostly, XML mapping files or annotations on getters, setters can be used to tell the JPA provider which fields on your object map to which fields in the DB. The most famous JPA provider is Hibernate, so is a good place to start for concrete examples. Other JPA implementations are OpenJPA, Toplink etc.

JDBC

Interview Online Test

JPA

Interview

JDBC is a standard for Database Access.

JPA is a standard for ORM.

JDBC is a standard for connecting to a DB directly and running SQL against it - e.g SELECT * FROM USERS, etc. Datasets can be returned which you can handle in your app, and you can do all the usual things like INSERTS, DELETES, run stored procedures, etc. It is one of the underlying technologies behind most java database access (including JPA providers).

One of the issues with traditional JDBC apps is that you can often have some crappy code where lots of mapping between datasets and objects occur, logic is mixed in with SQL, etc.

JPA is a standard for Object Relational Mapping. This is a technology which allows you to map between objects in code and database tables. This can "hide" the SQL from the developer so that all they deal with are java classes, and the provider allows you to save them and load them magically. Mostly, XML mapping files or annotations on getters, setters can be used to tell the JPA provider which fields on your object map to which fields in the DB. The most famous JPA provider is Hibernate, so is a good place to start for concrete examples. Other JPA implementations are OpenJPA, Toplink etc.

복습용 저장

이 항목을 북마크하거나, 어렵게 표시하거나, 복습 세트에 넣을 수 있습니다.

내 학습 라이브러리 열기

도움이 되었나요? 예 아니요

비슷한 비교 더 보기

아래에서 차이점 보기

아래의 모든 주제 비교를 살펴보거나, 위 검색창을 사용해 목록을 즉시 좁혀보세요.

집중 학습 경로, 모의고사, 면접 준비 콘텐츠로 실력을 키우세요.

JDBC vs JPA

차이점 비교

JDBC 과 JPA 의 차이

복습용 저장

관련 차이점

아래에서 차이점 보기

WithoutBook