Skip to content

Instantly share code, notes, and snippets.

@z3t0
Created April 30, 2018 02:36
Show Gist options
  • Save z3t0/92ad02056b2fbb388e360a2b92097b41 to your computer and use it in GitHub Desktop.
Save z3t0/92ad02056b2fbb388e360a2b92097b41 to your computer and use it in GitHub Desktop.
research on database

SQL vs NOSQL

  • SQL: relational, NOSQL: non relational
  • SQL: universal but defined schema
  • NoSQL: unstructured dynamic schema
  • SQL is vertically scalable, increased resources of one machine
  • NoSQL is horizontally scalable, increase number of machines
  • NoSQL can become larger and more powerful
  • NoSQL does not require a DBA (Database Administrator)
    • flexible and high performing
  • Will go with NoSQL because it has a dynamic schema, will switch to SQL later on if there is a reason to do so, such as performance gains

Choosing a database

  • mongodb: general recommendation
  • dynamodb: amazon managed service
  • Couchbase: often used for social services
  • redis: high-preforming in-memory database -> i think this is used on top of a more generic database

https://optimalbi.com/blog/2017/03/15/dynamodb-vs-mongodb-battle-of-the-nosql-databases/

DynamoDBMongoDBWinner
Free 200M Requests AmazonSelf hostedDynamo
Difficult to work with?Mongo library was easier to work withMongo
Security is managed by AWSSecurity is self-managedDynamo
  • It seems Mongo is easier to work with and so was given the recommendation
  • It is my opinion that Dynamo has more benefits that outweigh Mongo
  • Followup: how do I interact with dynamo from common lisp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment