Saving tracks (database integration)

waarzitjenu / server

Back-end server (API) of waarzitje.nu.

European Union Public License 1.2

12 stars 4 forks source link

Saving tracks (database integration) #3

Closed ricardobalk closed 4 years ago

ricardobalk commented 4 years ago

The current app only saves the last known location. There is no database that can save tracks.

raydwaipayan commented 4 years ago

For saving previous locations, we have two options:

1) A vector which stores all locations submitted so far in memory. (non persistent) 2) Db engine like BoltDB to store the entries somewhere in storage. (persistent)

Which are you aiming at?

ricardobalk commented 4 years ago

I was aiming at option 2. A persistent database that could save tracks even between restarts of the app. Preferably with multi-user support, or at least ready for it (see #2)

Could be BoltDB, I've just been reading into it. Depending on your experience with it, you could give it a shot.
Something like sqlite might also work (and sqlite could be opened with sqlite viewer apps, as a nice addition)
MongoDB could be an option, but that's a bit heavy.

What's your opinion on this?

raydwaipayan commented 4 years ago

Maybe bolt or sqlite. Mongo is way heavy for the current purpose.

Considering there is very little relation between data, (which are simply location entries), a nosql db might be the to-go here.

So perhaps bolt will be ideal.