Sensor temporal data: storage best practices

App Development
,
1

Hi everybody!
Considering +/- of moving lots of temporal sensor data to dgraph.
The data structure is simple:

  • sensor_id: i
  • timestamp: t
  • measurement: v

Shall I reflect the same structure in the graphql schema ( type Measurement {i, t, v} ) or there are better ways to structure/store such kind of data for optimal dgraph performance?
What are the best practices here?

2

I think for your case the entity is straightforward.

type Measurement {
    sensor_id: ID!
    timestamp: DateTime
    measurement: String
}

You can now get your hands dirty, there is nothing complex that you need to do. Unless you have a bigger goal and more entities to relate to. And in general, all existing practices in the GraphQL community apply to Dgraph’s GraphQL.

3

Thanks!