I am a big SQL fan but not all data has to be relational.
Let’s say I want the GPS coordinates of ten million vehicles every 5 seconds. I have a vehicle id, a timestamp, and coordinates. I do not care if a few writes get lost. Why does this have to be relational?
And perhaps I also record other info that may change from vehicle to vehicle. Perhaps just values that are true if present. DoorOpen, BrakeApplied, LightsOn, LightBarOn, EngineOn, etc. I may only be displaying this data in a UI. I may get different values from every vehicle or even every write. There is no “schema”. I mean, I can have a JSON field or something in my relational table? But this is not exactly relational anymore.
Correct not all data has to be relational but it will always eventually become relational. You will at one point want to pair that vehicle id to a vehicle and then again to something else.
A400 is at least relational.
MongoDB on the other hand…
I am a big SQL fan but not all data has to be relational.
Let’s say I want the GPS coordinates of ten million vehicles every 5 seconds. I have a vehicle id, a timestamp, and coordinates. I do not care if a few writes get lost. Why does this have to be relational?
And perhaps I also record other info that may change from vehicle to vehicle. Perhaps just values that are true if present. DoorOpen, BrakeApplied, LightsOn, LightBarOn, EngineOn, etc. I may only be displaying this data in a UI. I may get different values from every vehicle or even every write. There is no “schema”. I mean, I can have a JSON field or something in my relational table? But this is not exactly relational anymore.
Correct not all data has to be relational but it will always eventually become relational. You will at one point want to pair that vehicle id to a vehicle and then again to something else.