Lightning Talk: Use a Single Table Design today!

[yucheng11122017]

Topic: single table design
PUNCH: As my ex taught me if your relationship is bad, its better to be single. I choose to believe that this advice isn’t copium, and it applies in many cases, not just in my love life. If you are designing a database, this advise can apply to you as well! Introducing single table design!
Singleton?
Flame Elton?
WIIFY: The main reason for using a single table in DynamoDB is to retrieve multiple, heterogenous item types using a single request.
Agenda:

• What is single table design
• Example of single table design in DynamoDB
• Why you SHOULDN’T use single table design
  Key points:
• Reduce query time and computing cost
  o One query for multiple different items
• Single table design is fast for your SPECIFIC access queries
  o It isn’t flexible
• If ACID principles is very important and storage cost is very expensive
• Rather than a single table design, maybe its about using LESS tables instead?
  Call to action/big idea: Before designing your next database, think about the database needs and consider if you really need these tables?
  Impact:
  • Know: That single table design helps to reduce query time and cost
  • Believe: That single table design will improve user experience and save cost
  • Do: Learn about single table design and consider using it!

Lightning talk - Single table design.pptx

[yucheng11122017]

Updated slides
Lightning talk - Single table design Updated.pptx