MMDBs are intended to achieve insignificant response time, and also amazingly high throughput for performance critical systems. This is conceivable on the grounds that the information is spared and controlled in the structure utilized by the application, which evacuates overheads related to translation and caching. MMDB technology is fit for supporting application-level deployment, real time data management and most ACID properties.
The data structures and algorithms of MMDBs are solely intended to deliver data, event and transaction administration in the application level. At the point when contrasted with fully cached relational database management systems, MMDBs make utilization of fundamentally less CPU. MMDB technology does not utilize magnetic disks, as the location for essential database storage. Rather, the magnetic disks are utilized for tolerance and recuperation. A workstation's main memory obviously has diverse properties from that of magnetic disks, and these contrasts have significant suggestions on the outline and performance of the database system.
1) The access time for main memory is orders of magnitude less than for disk storage.
2) Main memory is normally volatile, while disk storage is definitely not. Notwithstanding, it is conceivable to develop nonvolatile main memory.
3) The disks have a high, fixed cost per access that does not rely on upon the amount of data that is retrieved during access. Hence, disks are block – oriented storage devices. Main memory is not block oriented.
4) The format of data on a disk is substantially more basic than the design of data in main memory, since sequential access to a disk is speedier than the random access. Sequential access is not as essential in main memories.
5) Main memory is normally directly accessible by the processor(s), while disks are most certainly not. This may make data in main memory more vulnerable than disk resident data to programming failure or software errors.
