2009/11/17 Rickard Öberg <[email protected]> > On 2009-11-16 11.14, Jacek Sokulski wrote: > >> I think it is quite important. Two points that raised most discussions >> in our team was integration and lack of RDBMS persistency. It is not the >> point if Spring or the RDBMS persistency is good or bad (anyway I think >> with Qi4j RDBMS persistency many developers would not found in DB what >> they had expected), but of human habits (and sometimes corporate policy) >> - it is easier to give up one habit at a time than five. It would be goo >> to have Spring integration HowTo, I'll try to play with it and write >> some points. >> > > One question about RDBMS: what are the particular reasons you need it? I've > seen many options, and am curious about your case. Is it ACID properties, > integration, reporting, backups, etc.?
1. ACID - although not quite sure if it is real requirement or just habituation ... 2. reporting - although can set separate RDBMS for reporting/integration 3. risk management - no much experience within our team with non-relational DB, not sure of maturity of such solutions (e.g. see the problem with RDF indexing); Customer requirements - some customers have requirement to use only one DBMS (usually Oracle), e.g. a couple of years ago we have lost a contract just because we have used a hierarchical DB not relational. Patterns like CQRS can probable solve technical problems but policy, habituation and experience is a little more tricky. Jacek
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
