title: How does Spring Data JPA differ from Hibernate for large projects?
body: <p>I am having a hard time deciding if I should stick with Hibernate for a new project, or get my feet wet with JPA and the new Spring Data implementation.</p>
  
  <p>Is the Spring Data framework intended for large projects or small projects with modest query requirements? </p>
  
  <p>While I certainly see the advantage in code reduction by using the <code>@Query</code> annotation, what do you do for dynamic queries? What about when you want to implement a save() method that's quite complex? </p>
  
  <p>The documentation says to make a Custom interface and implementation that your main repository implements, but what if you need to access any super methods on the crud repository itself? The crud repository implements the custom one - not the other way around. It seems like an odd design.</p>
  
  <p>I am very uncertain whether this framework will meet the challenges of complex and large applications. I've never ran into many problems with Hibernate, and I'm considering sticking with the good old reliable rather than go with Spring Data JPA. </p>
  
  <p>What should I do? What unforeseen complications and costs will I encounter if I go with Spring Data JPA?</p>