ORM - Guidance, Input, Views etc

[Louis Botes]

Hi All,

I am looking for a little guidance/input etc from someone with a bit more experience than myself.

Here's the story.

We have a few systems internally which drives a number of business activities.  These systems all share the same set of databases.  The systems as well as the databases are constantly changing as things grow and improves etc.

In summary the key systems include a Billing component, data exchange and mediation component, reporting element and service provisioning service.  These are a blend of PHP based front-ends and Java servers (RESTFul web services).

With all the interaction all the server components has to the database, I want to build a java library separately to contain a data abstraction type component we can simply include as another Maven dependency at build time – this makes it so much easier when we add features and massively reduces the code written all over the systems to access our databases with.  

However, since I am not the worlds most experienced Java developer, I was hoping to gain some insights into what could make my life easier, should I look at getting to know Hibernate?  It looks great but complicated, should I look at rather using something simpler?  I want something that is easy to implement and that can manage changes to Database structures without too much hassle.  I do need it to be powerful and it has to have very little overhead when processing very high volumes of transactions.  And of course it must generate code that is – erm – easy to read and modify as well as structure in terms of placement within the application structure.

Let me know your thoughts, feelings and experiences please.

--  Louis Botes Support +27 (0) 83 307 9512 Office     +27 (0) 21 488 3940 Fax          +27 (0) 21 422 0597 Mobile +27 (0) 82 907 0980 www.evosat.com P Please consider the environment before printing this e-mail

[Jason Purcell]

I like using JPA with Hibernate as a provider.

Very easy to set-up.  Minimal XML configuration.

Annotations make life much easier.

JPQL is very simple to use as well, although it was not needed that often in the apps I wrote.

I had trouble working with criteria though, but I was teaching myself as I went along.

--
You received this message because you are subscribed to the Google Groups "CTJUG Forum" group.
To post to this group, send email to CTJUG...@googlegroups.com
To unsubscribe from this group, send email to CTJUG-Forum...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/CTJUG-Forum
For the ctjug home page see http://www.ctjug.org.za
For jobs see http://jobs.gamatam.com/

[Herman Lintvelt]

JPA with Hibernate gets my vote as well.

Writing custom JDBC code is soooo last century... ;-)

[Louis Botes]

Thanks – Appreciated – Checking it out now…

--  Louis Botes Support +27 (0) 83 307 9512 Office     +27 (0) 21 488 3940 Fax          +27 (0) 21 422 0597 Mobile +27 (0) 82 907 0980 www.evosat.com P Please consider the environment before printing this e-mail

[Mike]

On 15/06/2011 10:09, Louis Botes wrote:

> should I look at getting to know Hibernate? It looks great but
> complicated, should I look at rather using something simpler?

Yes, you should. http://eodsql.dev.java.net/

In use everywhere that Hibernate just get in peoples' way.

--
mike morris :: mikro2nd (at) gmail (dot) com

http://mikro2nd.net/
http://mikro2nd.net/blog/planb/
http://mikro2nd.net/blog/mike/

This email is [X]bloggable [ ]ask-first [ ]private

[Matthew Marinovich]

Yep - I'd go with JPA as well.  Since you have existing databases I would look at reverse engineering the JPA entity classes using something...e.g. eclipse link, netbeans etc.

--
You received this message because you are subscribed to the Google Groups "CTJUG Forum" group.
To post to this group, send email to CTJUG...@googlegroups.com
To unsubscribe from this group, send email to CTJUG-Forum...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/CTJUG-Forum
For the ctjug home page see http://www.ctjug.org.za
For jobs see http://jobs.gamatam.com/

--
Matthew Marinovich
matthew.m...@gmail.com
Mb +27 (0) 79 572 9308

[Louis Botes]

What about Firestorm?  Is it worth the amount of cash to fork out?

--  Louis Botes Support +27 (0) 83 307 9512 Office     +27 (0) 21 488 3940 Fax          +27 (0) 21 422 0597 Mobile +27 (0) 82 907 0980 www.evosat.com P Please consider the environment before printing this e-mail

From: Matthew Marinovich <matthew.m...@gmail.com>
Reply-To: <ctjug...@googlegroups.com>
Date: Wed, 15 Jun 2011 14:11:04 +0200
To: <ctjug...@googlegroups.com>
Subject: Re: [CTJUG Forum] ORM - Guidance, Input, Views etc

[Mark van Wyk]

EoDSQL is great, but beware. No documentation.

Mark van Wyk

Email: ma...@foxbomb.com

Mobile: 082 831 9227

"Before printing this email, please consider the animals and eat less of them"

On 15 June 2011 13:23, Mike <mikr...@gmail.com> wrote:

[Yusuf Jakoet]

MyBatis?

-- 
Yusuf

[Louis Botes]

As I noticed yes.

Looks like a weekend of fun ahead for me... So far the options to review:

EoDSQL, jpa + hibernate and firestorm

But it seems the number of tools out there which could do what I need have no limits. Where to find the time to check the lot out?

Sent via my CrackBerry...

---

From: Mark van Wyk <ma...@foxbomb.com>

Sender: ctjug...@googlegroups.com

Date: Wed, 15 Jun 2011 18:22:00 +0200

To: <ctjug...@googlegroups.com>

ReplyTo: ctjug...@googlegroups.com

Subject: Re: [CTJUG Forum] ORM - Guidance, Input, Views etc

[Mark van Wyk]

My vote: Start with basic simple hibernate annotations. Should be able to get something up in an hour or 2. Seems that the other frameworks are based on really similar concepts so changing your mind shouldn't be too difficult.

Mark van Wyk

Email: ma...@foxbomb.com

Mobile: 082 831 9227

"Before printing this email, please consider the animals and eat less of them"

[Bruce Stewart]

Hi Louis,

My suggestion is JPA using hibernate as the implementation. The learning you will go through in order to learn hibernate/JPA is really one of the best investments you can make (in terms of personal learning). It will make you a more valuable programmer and there is plenty of help and documentation about to help you get up and running quickly. You can also be guaranteed that you won't need to replace the JPA code in 2 years because the API/technology will be around for a lot longer than that. JPA based code will scale as well as anything else out there. From a performance point of view, a JPA/hibernate solution would probably meet 95% of your needs.

My 2 cents