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.

Sign up for GitHub

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

Jump to bottom

NoSQL vs RDBMS backend?? #1

Open

atulsaurav opened this issue Jul 29, 2017 · 3 comments

Assignees

atulsaurav commented Jul 29, 2017

Since we are on AWS, why don't we use a simple NoSQL data store like DynamoDB vs our current plan of RDS?

It will simplify lots of scenarios.

Contributor

skvasant commented Jul 29, 2017

Gr8 idea @atulsaurav except we have like another 6hrs before showing something works, therefore lets leave this as a suggestion for now ;)

Member

djfurman commented Sep 29, 2017

Here's a thought...

RDS for Static Content
ElasticCache/Redis for Caching Content
DynamoDB for final wishes
Lambda for BE processing
API gateway for Lambda Invokation
Cognito for user authentication
S3 for static hosting (consider CloudFront)
Route53 for DNS
Azure Face for Facial Recognition
Glacier for Long Term Photo storage

Member

djfurman commented Sep 29, 2017

Yay serverless!

djfurman assigned jsonRUHLS and djfurman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment