For the purpose of this project, we don't actually need all the pricing data all the time. If the goal is to use the data for training a model, then we can store the data, train, and then flush the data on a set schedule. It should be enough to store the past 60 days worth of data, a big enough overlap of the last training time.
Pros:
don't need two data stores
simplifies code as we already use postgress
Cons:
lose out on the cool influx dashboard
can't create a pricing server (not really a goal ATM)
For the purpose of this project, we don't actually need all the pricing data all the time. If the goal is to use the data for training a model, then we can store the data, train, and then flush the data on a set schedule. It should be enough to store the past 60 days worth of data, a big enough overlap of the last training time.
Pros: