I am creating a Java EE project that has over 40 database tables. Which persistence API is better to use for such a project: hibernate/jpa etc..
I could not find any post corresponding to this scenario even on google.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am creating a Java EE project that has over 40 database tables. Which persistence API is better to use for such a project: hibernate/jpa etc..
I could not find any post corresponding to this scenario even on google.
You have lots of options, and your question is not easy to answer without knowing more about your specific requirements.
When you want to get “persistence” up and running fast, use JPA. JPA is optimal for you if you don’t care about SQL or the relational model too much, but instead want to “persist” data and perform CRUD (OLTP). Some sample implementations:
When you want to control your SQL, use non-standard frameworks. These may be better suited when you want to have fine-grained control over the queries that are emitted by the framework, because you want to perform much more than “CRUD” (i.e. OLAP):
When you want to do it all on your own, use JDBC, directly (which is also a “persistence API” in a way)