Casper Bang wrote: >> Relational Databases like Oralce, SQL Server, MySQL.. >> > > Also worth mentioning, there exists languages today with such mapping, > query and persistence integration that there's really no need for a > dedicated OODB and the associated versionability/flexibility problems. >
agreed... sort of. versioning is and always will be a problem. I think the evolving model is one where all things will be kept in memory or something like memory at all times. Maybe after years of hoping, the file system will start to go away. We are already seeing diskless deployments based on redundancy at all levels combined with replicated clustering that are proving to be more inject less latency and provide more resiliency than disk based solutions. Kirk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
