CODEWITHSUNDEEP
mysqlmongodbredisdatabasenosql
Steven
Steven

Reputation: 3894

Suggestion for write frequently, read rarely database

I have an application server which writes frequently to a database and reads it in the near future, but then very rarely that data entry is read.

What is some good databases optimised for this kind of access? I am currently using MongoDB but I think that probably isnt the best choice in this case.

I am open to relational DBs (i.e. MySQL), MongoDB, Redis, etc.

P.S. Seems it's easy to answer this question for read frequently DB access, but hard to find information on this specific case.

Upvotes: 2

Views: 1230

Answers (2)

Siva
Siva

Reputation: 2811

This is very generic question, We need to know more details

  • Size of Database
  • Data growth, How much 10GB per day / 200GB per month ?
  • Is it a OLTP Application or OLAP Application ?
  • What is maximum number of concurrent transactions / users ?

Apart from it, Since you have mentioned data is rarely read beyond a certain point

  • You can always look at options for Archival (Cleaning up based on duration - Monthly basis / Yearly basis)
  • Parititioning is also another option, for faster retrieval

Again the option for going for SQL or NOSQL is based on

  • Consistency
  • If you have a fixed schema I would suggest you to go for Relational DB
  • Concurrency aspects, Based on need you need to decided SQL or NOSQL (example - online banking i would suggest RDBMS, For product reviews/comments storing for a site, I am ok for NOSQL as this does not need any concurrency handling)

You need to provide more details on your database need in terms of functionality, data volumes, data usage and growth aspects

Hope it helps...

Upvotes: 1

Ilmari Karonen
Ilmari Karonen

Reputation: 50328

Since you mention MySQL, you might want to look at the ARCHIVE storage engine.

Upvotes: 0

Related Questions