Currently it's a bit annoying, even if just for development purposes, to lose the entire session storage (namely that one single in-memory TVar), everytime I restart the server. I'm also wasting lots of API quota just for doing the OAuth flow again and again.
Top considerations:
SQLite
Redis
Leaning towards SQLite, because:
I don't want the hassle of starting up multiple processes, and
I also like the persisted nature of it, safe from process crashes.
The implementation can be easily abstracted over which particular storage backend. However, this creates a non-trivial deviation from the upstream scotty-session package, which means I may be totally on my own now, and need to own all of that currently ~100 lines of a module.
Currently it's a bit annoying, even if just for development purposes, to lose the entire session storage (namely that one single in-memory
TVar), everytime I restart the server. I'm also wasting lots of API quota just for doing the OAuth flow again and again.Top considerations:
Leaning towards SQLite, because:
The implementation can be easily abstracted over which particular storage backend. However, this creates a non-trivial deviation from the upstream
scotty-sessionpackage, which means I may be totally on my own now, and need to own all of that currently ~100 lines of a module.