-
Notifications
You must be signed in to change notification settings - Fork 36
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
Flask-Secuity using Flask-Dynamo for persistence #1
Comments
Heyo! Thanks for the ticket. I didn't really think about that -- I'll look into it! I've never really thought about using dynamo for storing user data, as it's not really the best choice (I mean, it could work, but it's not ideal in many ways). It might be worthwhile, however, if there's people using it for that. |
Well the way I see it with Flask-Security already using Mongo DB as a standard persistence layer and Dynamo DB's increasing capabilities like global and local secondary indices, all Dynamo really needs is a JSON attribute type and it'd be perfect. I also know that there are many people who use DynamoDB for their user session state since it can handle the heat of user-session interactions at any scale. Hence the idea to explore this connection between modules now. |
That makes perfect sense to me -- I wasn't aware that so many people were using Mongo with it currently. In that case, I'll definitely look into / start working on that! I'm going to have some free time next week, so I'll likely dive into it then! Would be uber happy to have someone look things over though ^^ |
Just let me know when you have a branch you'd like another set of eyes upon. |
Have you thought of working with the Flask-Security framework to add Flask-Dynamo as a data persistence layer? If you're interested in such a thing I'd be interested in helping.
The text was updated successfully, but these errors were encountered: