473 karma · joined January 27, 2012
It becomes way more difficult when you have N servers all of which could potentially serve the same data. Local caches could then, yes easily become stale, and even if you have a propagation mechanism, you couldn't guarantee against network failures or latency issues.
But suppose you have an HA redis instance that you store your cached data in. Even with a write-through cache, you basically need to implement a 2-phase commit to ensure consistency.
Why?
Mostly for the challenge. [hulkholden] spent ~25 years (on and off) working on N64 emulators and writing one in JavaScript gives [him] the opportunity to expand [their] comfort zone and learn something new. It's a good showcase for how powerful modern browsers have become.
Getting a nil where you are supposed to have an Optional.