REP tasks are unique, individual, one-time tasks (coming from Issues requested by operations or MOs requested by Maintenance, Engineering, or any other department).
These tasks are not repetitive like PMs or PdMs -> It is correct to store data about PMs and PdMs in DB because I will be using this data every time.
It is useless to store REP tasks in the DB -> DB is semi-permanent data -> I don't think REP tasks should be stored there -> We should try not to store them in the DB. If they need to be stored somewhere during dashboard generation, they can be stored in cache.
REP tasks are unique, individual, one-time tasks (coming from Issues requested by operations or MOs requested by Maintenance, Engineering, or any other department).
These tasks are not repetitive like PMs or PdMs -> It is correct to store data about PMs and PdMs in DB because I will be using this data every time.
It is useless to store REP tasks in the DB -> DB is semi-permanent data -> I don't think REP tasks should be stored there -> We should try not to store them in the DB. If they need to be stored somewhere during dashboard generation, they can be stored in cache.