Read and Write Considered Harmful

Read and Write Considered Harmful

ACCU Conference via YouTube Direct link

Consistency • Do all copies of the data need to be exactly up- to-date right now

15 of 22

15 of 22

Consistency • Do all copies of the data need to be exactly up- to-date right now

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Read and Write Considered Harmful

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Reads
  3. 3 Dependencies
  4. 4 REST APIs and rules
  5. 5 REST APIs and schemas
  6. 6 REST APIs and processes
  7. 7 Typical system scaling path
  8. 8 Scaling problems • Partitioning or sharing works to an extent
  9. 9 Avoid sharing mutable data
  10. 10 questions about data access
  11. 11 Non-primary key access - Finding items by value, not by key
  12. 12 Range scans and sequential access - Requires ordering Leoperators, ordering costs • Requires iberators/cursors/traversal state
  13. 13 Read/write ratio
  14. 14 Working set size and skew • How much of the common data will fit in main
  15. 15 Consistency • Do all copies of the data need to be exactly up- to-date right now
  16. 16 Reader/writer vs data flow
  17. 17 Sync vs async systems
  18. 18 Data flow and sync/async
  19. 19 Content management example
  20. 20 Larger example
  21. 21 Command Query Representation Separation (CORS)
  22. 22 CORS examples

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.