When should I consider using a in memory database and what are the issue to look out for?

Question

I was just think that now it is common to have enough RAM on your database server to cache your complete database why are the specialist in memory database (e

Answer 1

Data processing needs are getting more complex and the product ecosystem is evolving to meet these new needs. Disk-based RDBMS, in-memory cache, and in-memory databases are used to satisfy different needs. You should go with what suits your need -

Traditional RDBMS: Your MySQL cluster is fast enough, easy enough to maintain, and you like having the reliability of ACID-compliance.

In-memory distributed cahce: Your application needs to do fast reads and writes without worrying too much about consistency or complex transactions.

In-memory RDBMS:

1. (Speed): Your application needs to process data/requests faster than your disk-based database can.
2. (Complexity): You need to make complex transactional reads and writes with joins and aggregations and like to use the power of SQL.
3. (Scalability): You need to scale your database horizontally without downtime.
4. (Maintainability): You need the database to provide high availability, replication, load-balancing and disaster recovery without adding to your maintenance chores.
5. (Caveat): Your data should fit in memory (typically in terabytes).