Not too far out, no. A document database can do this, but time-series data is pretty easily done in an RDBMS also.
On Tue, Apr 1, 2014 at 6:20 PM, <[email protected]> wrote: > Hi, > > I'm going to go way out on a limb here and say that typical time-series > data is not an optimal fit for graphs/OrientDB. > (I'm not a member of OrientDB and the will hopefully prove me very wrong > as I could use that as well) > > I'm using Druid.io for the our TSData. > > Regards, > - Stefán > > > On Tuesday, 1 April 2014 15:38:27 UTC, NY wrote: >> >> Hi all, >> I need some advices about the schema to adopt for an application that >> manages a certain amount of data coming from remote sensors (IoT). >> My doubt is about the relation between a sensor and the many measures it >> produces (i.e. temperature=10, timestamp=1234567890). >> I would be asked to satistfy a query like: give me the average value of >> all the temperature sensors in a specific time interval) and give me the >> last measure of the sensor xyz. >> What's the most efficient way to implement the relation on OrientDB >> regarding the above scenarios (queries)? >> Thank you >> ny >> > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
