I want to store a high computational parameter to prevent its recomputation, should I use cache or a database? This parameter need to be updated frequently to maintain consistency

Question

1.00/5 (2 votes)

See more:

, +

I want to store a high computational parameter to prevent its recomputation. But this parameter needs to be updated frequently to maintain consistency, should I use cache or a database or is there any other better solution for this?? I am using a mongodb database though.

What I have tried:

Based on my research, I found that caching is good for use cases where we need to store high computational parameter which is frequently accessed?? But I am confused about the impact of frequent update on this scenario.

I am a beginner in system design and its related concepts, please help me.

Posted 29-Sep-23 2:20am

Bhanu Arora 2023

Updated 2-Oct-23 2:29am

Deeksha Shenoy

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2023-09-29T04:18:00

All a Cache is is memory that is "closer to the processor" - often part of the same chip, and which is faster for the processor to access that having to go outside the CPU to main memory top get the value.
And all frequent updates will do is ensure that the value stays in cache.

If you want to create your own cache within your app, that's fine - just decide where it needs to be used and updated because Javascript code is executed on the client, and for the server to get near it means a round trip across the internet, and the same thing for the reverse - if you store it on the server and the client needs it, that's another round trip.

A database is generally outside the server so storing it there and updating it frequently will generate a lot of traffic, and that could consume a lot of your MongoDB server bandwidth, slowing everybody using it down. And then, if it's used or calculated at the client, you have two round trips involved: client <-> server <-> DB server. More bandwidth, more slowdown.

DB's are for things you need to remember once your app has closed so it can be accessed again when it reopens. Caches are volatile data that is discarded when your app closes (unless your app specifically saves them - maybe to a DB - when it closes).

We can't tell you "use this" - it neds way too much knowledge of your systems and how they anad your app work that we just don't have access to