Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Hibernate vs JDO

 
K Huang
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am new in this area. A few months ago I started looking for a new job. That is when I heard Object Mapping stuff. Then I heard Hibernate and JDO.
During several interviews, I was asked about these stuff.

Hibernate or JDO ? Which one is more popular ? I mean which skill is more marketable ? If a company is using Hibernate, will it hire somebody knew JDO but not Hibernate ?

Do I really need to read a thick book to learn these skills ?
 
Naina Si
Ranch Hand
Posts: 134
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Even I would like to know about this stuff. i have not used any of these. Appreciate your reply.
 
Robin Roos
author
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi

That's an impressive list of certifications, but industry seems far more interested in experience. Even if you haven't used OR Mapping technologies on real projects you should probably read around the subject a little and do some playing at home. You should be in a position to tell your boss what OR Mapping is, how the various technologies compare at a high level, whether your development team would benefit through their use, and why.

It will probably be some years before OR Mapping makes it into the certification syllabus, but it is a technology that is of significance to industry today.

Cheers, Robin.
 
Robin Roos
author
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
On reflection I don't think I answered your specific question, so here goes:

If I was hiring for a contract position I would expect intimate knowledge in, and direct experience of, my project's technology stack. If the project used JDO and the developer was going to be working with code that touched the JDO API then I would require them to know JDO. Same goes for Hibernate - contract staff must bring specific experience to the team.

If I was hiring permanent staff (for a similar role) then I would look for an appreciation of object persistence who could be trained on-project in the specific technology we use. In such cases I would accept good Hibernate experience for a JDO role, and vice versa.

Learning JDO is not difficult and the books are not too thick. Mine is available as a free PDF download from www.solarmetric.com - enjoy!

Kind regards, Robin.
 
K Huang
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Robin !
Shame on me. An interviewer found out I had no exposure to OR Mapping, he immediately concluded that I did not have enough experience. I have CS BS&MS and 13 years industry programming experience(6Y in Java), plus these certifications, still be considered not experienced. This proves OR mapping is important.

Thanks for your free book. I think I got to buy your printed book. It is hard to read on the screen.

2 more questions:
No1.: In www.solarmetric.com:
"Kodo JDO provides access to relational databases through the JDO standard, enabling Java developers to use existing relational database technology from Java without needing to know SQL or be an expert in relational database design"
If our team member are all good at SQL too, will JDO or Hibernate bring any extra benefit to us ?

No2.: Why won't u hire a Hibernate contractor to work on JDO ? Can't he/she learn JDO in a day or 2 ?
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can I reply to #1.

Even though you might be the wizard of SQL, writing all those queries to run in your code just takes way too long, especially if you have lots of tables, now a three table application, yes, just writing JDBC and queries are fine, but you still then have to take the result sets and create your DTO's and mapping the fields to your instance variables. Lot of icky, not fun code to write.

Whereas with JDO or Hibernate, they handle the SQL, and creating those DTOs all for you. I think that is a huge benefit, big enough to save millions of dollars on large projects.

Mark
 
K Huang
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I see. Thanks Mark !
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic