On 15/04/2011 01:26, Ate Douma wrote:
I think we really should start simple and get something to "play" with
ASAP.
As long as we're still in the "prototyping" phase (which I think we'll
be in for a while), I really don't care a lot about too strong upfront
design principals.
+1
In cases like this (Interface Vs POJO)where there are two well reasoned
but conflicting sets of opinions it's probably best to just get on with it.
The problem is how to pick which route to "get on with".
The key deciding factor (at least for me) is which will get us to the
point of having something to show the "customer" the quickest without
closing off the alternative route entirely.
So, I'm +1 to start with just JPA annotated POJOs, but keep an open mind
for possible other persistence back-end integration and make sure that
will remain doable. If that ends up requiring refactor to interfaces
later, fine too.
+1
The key here is the door is always open for someone to make a case for
the customer needing (as opposed to "possibly wanting") NoSQL.
Ross
