Skip to main content

Why In-Memory Database

An in-memory database (IMDB) is a database whose data is stored in main memory to get faster response times. Currently there are 3 most popular storage systems for data/database, RAM, SSD and HDD.

RAM performs random reads/writes at 100 MB per second. Sequential reads/writes are even faster 1 GB per second and higher. An SSD is slower than RAM. Random access time is a fraction of a millisecond (1e-5 seconds): we can randomly read around 10,000 blocks per second. Random access time is 10 milliseconds (1e-3 seconds), which is 100 times slower than an SSD. If we talk about price on average, each storage type is ten times more expensive than the previous one. An HDD is the cheapest storage type, an SSD is ten times more expensive than an HDD, and RAM is ten times more expensive than an SSD.

So If we need access time of 1 ms or less, choice is RAM. Different database vendor have different size limits. There some popular use cases where In-memory database is being use.

1. Session Cache / Caching
2. Queues
3. Real-Time Analytics etc

Thanks for reading
Plz dont forget to like Facebook Page..


Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription