Re: Informations about prevalence

Hi Valerio :)

My question is: would anyone use a transient relational database for a
system that would never have persistence requirements?

See you, Klaus.


On Sat, Jan 29, 2011 at 4:56 PM, valerio barbagallo
<[email protected]> wrote:
> Hello Klaus,
> nice to hear you again.
>
> I'm glad that you found my thesis interesting, although I'm not working
> anymore with in-memory databases. Actually I'm now working in Reply, a
> consulting company which is partner of Oracle!
> I completely agree with all your answers. I would like just to point out
> that in-memory relational databases are not so useles:
>
> as i wrote in my thesis, if I remember well, relational IMDB could be useful
> for test purpose (obviously if you used standard SQL) to speed up all
> operations.
> relational IMDB can also be used as a default choice for applications that
> want to allow the user to switch to another relational enterprise
> database.For example JBoss uses HSQL by default.
>
> Regards,
> Valerio Barbagallo
> On Fri, Jan 28, 2011 at 8:38 AM, Klaus Wuestefeld
> <[email protected]> wrote:
>>
>> > Do you think prevalence can be seen as agile ?
>>
>> Yes. The prevalence architecture is much simpler and allows greater
>> freedom of choice for data structures and algorithms.
>>
>>
>> > Do you think the diffusion of agile methods could give a boost
>> > to prevalence ?
>>
>> Yes. Agile teams are more open to new ways of thinking about architecture.
>>
>>
>> > Thanks a lot for your answer !
>> >
>> > What caracteristics of prevalence can be seen as agile ?
>> > Could you detail ?
>>
>> Extremely easy set-up and deploy. No object-relational mismatch.
>>
>> http://www.codinghorror.com/blog/2006/06/object-relational-mapping-is-the-vietnam-of-computer-science.html
>>
>>
>> > I found this thesis.
>> > http://error0.altervista.org/university/tesi%20magistrale/thesis.pdf
>> > Have you ever heard about that before?
>>
>> No, I had not. It is a very nice roundup of in-memory databases union
>> Prevayler. I have copied Valerio, the author, in this email.
>>
>>
>> > Page 158, he says some interesting things about PICO4 and HSQLBD.
>> > What do you thing about that ? Is prevalence better than this
>> > new notions?
>>
>> HSQLBD is relational. Nobody uses the relational paradigm if not
>> forced to use it for persistence purposes. Nobody in there right mind
>> writes a transient app, such as a browser, a router or a game, keeping
>> its data in relational tables in RAM and accessing it through SQL, do
>> they?
>>
>> PICO4 produced better transaction throughput numbers than Prevayler
>> because, from what the thesis says, it does not physically sync
>> transactions to disk. So if one has non-important transactions, PICO4
>> is a good choice.
>>
>> Turning off Prevayler's physical sync to disk yields similar results.
>>
>> See you, Klaus.
>
>

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org