Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore backend store setup #483

Open
danschultzer opened this issue Apr 7, 2020 · 1 comment
Open

Explore backend store setup #483

danschultzer opened this issue Apr 7, 2020 · 1 comment
Labels
question Further information is requested

Comments

@danschultzer
Copy link
Collaborator

One thing that I keep thinking about is the backend store. Ref #392 #386.

Looking at the mix phx.gen.auth proposal PR, they put all tokens in the Ecto DB. I like that there's a single source of truth for the user struct. I would like to investigate how a better backend store could look, and see whether the current setup can be streamlined. Would be interesting to rethink the backend store from an Ecto perspective.

ETS and Mnesia still makes most sense to me. It's easier to keep in line with what NIST seems to argue for as well. Ideally session data isn't persisted, and application restarts will wipe out the state. Not ideal for how most web apps works, but it would be great to explore rolling deployments with Mnesia and no disk storage.

@danschultzer danschultzer added the question Further information is requested label Apr 7, 2020
@danschultzer
Copy link
Collaborator Author

danschultzer commented Sep 22, 2020

Pushing work for this with #392 and #567. Inching towards resolving this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant