On 3 November 2014 10:43, Mark Rogers mark@quarella.co.uk wrote:
Until last week I had zero understanding of NoSQL. I spent some time going through tutorials (using OrientDB - I have no idea how much of this is generic and how much is DB specific) and now have a broad understanding of a graph database, and the concepts of vertices and edges.
You're ahead of me - I've only used KV or Document NoSQL stores so far, and not OrientDB
I'm hoping for some advice on a sensible schema to get started on a specific application... ...So any guidance would be very gratefully received
Unless someone here has experience of Graph DBs, I'd suggest asking on the Orient forums.
But, if I were starting with a new data store, I would keep my object model as simple as possible to start with and begin by working out in detail how to search the data. This can then guide the layout of the data in the store, and how you index it (I understand that Orient has a couple of index options).
Also, I have no idea how well it would perform. A handful of samples every minute would be fine I am sure, but what it if were more like 50-100? And what it they were stored every second? That might not be relevant here but this is a learning exercise and I want to understand this stuff. (50-100 samples per second into a MySQL DB would be no problem even on a Pi, after all, assuming they were stored in a single record as described above.)
NoSQL stores are typically very fast, so I'd be surprised if you didn't get better performance than MySQL.
Best of luck and interested to know how you get on.
Cheers,
Ewan