10. NoSQL vs NewSQL
• NoSQL is a really bad label
• It’s not about SQL
• It’s about better performance or
scalability
• Sometimes we can live without ACID
22. The good parts
• Table based (each table is
independent)
• Schema free (except the Key)
• Really fast to find using Primary and
Range Keys
• Support for complex queries (Scan)
23. The “must know” parts
• Eventual consistency by default, with
high costs to ensure consistency.
• Must use SDK/API to access
• 64K is the max “row” size
• Complex queries are made using
Sequential/Full Table Scan (high cost)
24. The bad parts
• Very limited data types (text, number,
binary)
• No way to join tables
• More than 64k of data per item
requires “workarounds”
• It’s not possible to copy a table to
another one
25. Final considerations
Pros:
• Really fast using IDs
• Really cost effective
• Full managed is a
good idea
• A good option for
key-value situations
Cons
• Very limited with
types and joins
• Complex queries are
costly