Firestore是时间序列数据的不错选择吗? [英] Is Firestore a good choice for time series data?

查看:46
本文介绍了Firestore是时间序列数据的不错选择吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个小项目,涉及一些简单的财务时间序列数据,并且前端包含一些实时组件.我希望使用Firebase基础结构,因为它提供了很多东西而不必建立太多基础结构,但是经过调查,它似乎不是存储时间序列数据的好选择.

I have a small project involving some simple financial time-series data with some real-time components on the front end. I was hoping to use the Firebase infrastructure since it offers a lot of things without having to set up much infrastructure, but upon investigating it doesn't seem to be a good choice for storing time series data.

诚然,我在关系数据库方面拥有更多的经验,因此我可能会问一个非常基本的问题.如果我要使用Firestore存储时间序列数据,是否有人可以提供一个示例,说明如何构造它以进行有效的查询?

Admittedly, I have more experience with relational databases so it's possible I am asking an extremely basic question. If I were to use Firestore to store time-series data, could someone provide an example of how one might structure it for efficient querying?

我最好使用Postgres之类的东西吗?

Am I better served using something like Postgres?

推荐答案

最好的选择是使用时间序列数据库.似乎已经提到了Warp 10( https://www.warp10.io ).

Probably best bet would be to use a time-series database. Looks like Warp 10 has already been mentioned (https://www.warp10.io).

诸如warp之类的好处是可以查询数据库的时间部分.我相信Firebase仅比时间查询中的查询大/小.

The benefit of something like warp is the ability to query on the time component of your database. I believe firebase only has simple greater/lesser than queries available for time.

这篇关于Firestore是时间序列数据的不错选择吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆