Magic with In-Memory Database

Hi tech zombies,

My name is Kiran Vajrapu, and I am from ThoughtWorks.

I had another new scenario from my IT experience. This scenario is about an in-memory database. Earlier, I was part of a project at a leading aerospace company. In that project, we have one microservice that deals with database and performs data manipulation using stored procedures.

If we compared the performance of all microservices, this one would take more time to process the request. Perhaps the reason is that data is being manipulated in the database and transferred to the application layer.

After a few months, one of the junior members of my team suggested Inmemory. So I went through that In-memory technology. In-memory databases use RAM and traditional databases use hard disk for storage.

It’s fantastic if you’re familiar with in-memory technology. If not, go get the information from the internet. And this is my perception: if we use an in-memory database in the above service, it will save some time while processing the request. However, selecting technology based on experience, benefits, drawbacks, etc.

Conclusion: In-memory database (IMDB) stores computer data in a computer’s main memory instead of on a disk drive to produce quicker response times. We cannot replace traditional databases because RAM is expensive and there is a risk of data loss upon restart. but this depends on the product.