Answer the question
In order to leave comments, you need to log in
What base to choose, for indicators, let's say water (the data is constantly coming, the index is over time)?
Let's say there is some system that constantly writes.
But at the same time only one client writes.
But constantly.
The data will grow very quickly.
Redis is not suitable as although I don’t need a realization as such, but the RAM is an expensive thing for logs.
If you use a relative index, then it is logical to put indexes there for a while, probably better even there.
Time zone thank God is not needed.
But here the question can anyone advise what to read.
I'm not looking for someone to do it for me, just good advice on what to choose.
I mean what I have.
A large amount of data, an indicator, a time and maybe a year there.
No overhead for writing
. But there is for reading, since reports will be frequent.
Just what is the best choice?
As though the engineering approach, I will probably stop and on , though it will be very superfluous to me
The maximum in system 1 table will be or a dial-up.
Answer the question
In order to leave comments, you need to log in
Time series databases for such tasks. Aggregates / post-processing can already be stored in what is convenient
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question