Anyone know what's going on here?
I'd also like to mention that I regret my uncharitable phrasing in my original comment "…the most ungooglable and generic name they could have chosen…". While I do think more specific names might have helped in some ways, I can appreciate the difficulty in coming up with names for this kind of thing.
SQLite could scale to even quite large customers with this.
Another really compelling architecture is a DB per user, with partial/selective sync between the nodes. If you then couple this with a "local first" design, the "edge" just becomes an other local deployment that the users db can sync against. Collaborative apps, where the users have their own documents but can also share/fork them would align well with this.
I believe starting with "local first" and using the edge for sync and "online only" modes is going to become the default for a significant number of apps moving forward. SQLite with CRDT based syncing and merge conflict resolution is the way to do this. There are a couple of exciting projects working on this:
I took it as a very interesting and profound discussion about the role of games and fantasy in our lives as adults after playing it from a different perspective as kids. The dialogs during the ending are very well thought and thought-provoking. The role of Elaine in it is special.
I loved the whole game, but the ending brought it to a complete new level for me. It’s probably something that I’ll want to play again a few years from now.