Re: #liveDB server, research and upcoming webinar on In-Memory Database Systems
Robert Friberg <[email protected]>
| Newsgroups | gmane.comp.java.prevayler |
|---|---|
| Message-ID | <04CBB7B6F20119479B70F3ED6355740102D532@AMSPRD0402MB112.eurprd04.prod.outlook.com> |
> Nice to see research being done :) > I am concerned about the terminology. I'm not *that* concerned about terminology, I'm *more* interested in seeing the technology spread and software engineering escape the dark ages. The terminology, imho, should aid this goal more than being absolutely consistent. >Do you guys call a prevalent system (prevalence layer plus > application) an "in-memory database system"? I would. Yes, I agree. And I think "System Prevalence" and "Prevalent System" should be at the center of the concept map. "Object Prevalence" shou > Do you call a prevalence layer (prevalent system minus application) > an "in-memory database system"? I wouldnt. The term layer implies a layered architecture. We prefer "Prevalence Engine". The engine is a component and needs an application context to be called a system. > Would you call an application using a traditional RDBMS with >enough cache to hold all data in RAM an "in-memory database system"? If not, why not? No. RDMBS architectures are page and disk centric. They are designed to map fixed size pages to block based devices. I would argue that a true in-memory database architecture is designed specifically to with the speed and random access nature of RAM. We might call this a memory centric or memory based database architecture? I recall reading Main Memory somewhere, this is perhaps better because disk is also memory, right? Robert Friberg 0733-839080 http://livedb.devrex.se http://livedomain.codeplex.com http://devrex.se http://www.linkedin.com/in/robertfriberg ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion _______________________________________________ "Databases in Memoriam" -- http://www.prevayler.org