You're Building a Distributed System!
2 likes1,212 views
The document discusses the different types of state in a distributed system, including ephemeral, permanent, and semipermanent states. It explains how data is handled in the browser and server environments, addressing the implications of consistency, availability, and partition tolerance (CAP theorem). The document also highlights approaches to manage data synchronization and offline capabilities using technologies like CouchDB, PouchDB, and Firebase.
You're Building a Distributed System!
- 1. State
- 8. You’re Building a Distributed System!
- 13. State
- 15. Ephemeral State
- 16. Local to the user’s browser. Cleared on page refresh. Not persisted to a server.
- 18. Permanent State
- 19. Persisted to a server. Written to disk.
- 21. State in Ember
- 22. Application
- 31. Lives in the browser. Transitory. Written to disk.
- 35. Synchronization
- 42. Browser Server
- 43. Computer A Computer B
- 44. Computer A Computer B Computer C
- 45. Computer A Computer B Computer CComputer D Computer N
- 46. CAP Theorem
- 48. Consistency
- 49. All nodes have the same data.
- 52. Availability
- 53. The software is fully functional.
- 58. The choice between being consistent or available.
- 60. Browser Server Unavailable + Consistent
- 61. Browser Server Available + Inconsistent IndexedDB (Semipermanent)
- 62. Going Offline
- 64. Back Online, Time to Sync
- 67. Why This Matters
- 68. Go offline Minimize data loss Zero latency UIs WIP (Work in Progress)