3 ms·
Eh materializing data upon mutation can bring you some gains if your product does like one thing and needs to do it very fast. But as soon as you get complex tr
by avereveard 3y ago
Eh materializing data upon mutation can bring you some gains if your product does like one thing and needs to do it very fast. But as soon as you get complex transactions with things that need to be updated in a atomic write or you want to add a new feature that needs data organized in a different way then you're in trouble.
Also deeply unsatisfied of "just slap an index on it" that was lightly trow around on the part about building an application. The index is a global state, it was just moved one step further down the layer.
- ColonelPhantom 3y ago> it was just moved one step further down the layer And therefore, crucially, you don't need to manage it yourself anymore. The only thing you need to do is tell the system what to index (which is code, not state/data).
- avereveard 3y agoBut I don't manage databases either, management is a poor differentiation
- ColonelPhantom 3y agoYou do manage the state of your database. When you do an UPDATE, you explicitly change the state. The statefulness of an index, however, is merely an implementation detail. A database without indices would be in the same state, and behave the same (except much slower). This means that the state is not important for the semantics of the datastore, unlike with a regular database.
- avereveard 3y agowhen I do an update I don't do a global state transition tho.