Hacker News new | past | comments | ask | show | jobs | submit login

But a relational database is great for that.

  select *
  from prices
  where symbol = any (?)
  and timestamp >= ?
  and timestamp < ?
I've worked at a couple of places where we kept price data in relational databases and did pretty much this.

The only way to beat a relational database here would be in performance. Because of course, for a specific use-case, you can always write a specialised data store that is faster than a general-purpose one. But the performance advantage might not be enough to justify the cost. If you're talking about storing every tick on an exchange, it might be, but if you're storing close prices, probably not.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: