3 ms·
Fragmentation comes with open source. State management is fragmented on the backend as well: PostgreSQL, MongoDB, Kafka, Redis, Dynamo, Influx, etc...it's just
by chrisco255 6y ago
Fragmentation comes with open source. State management is fragmented on the backend as well: PostgreSQL, MongoDB, Kafka, Redis, Dynamo, Influx, etc...it's just that state management fundamentally has different trade-offs based on how you structure it (and may involve 1 or several of these).
If your app is simple, you don't really need a separate state-management solution (just use the built-in React useState and useReducer hooks). If it's complex, you have a choice to make, but that's a fundamental issue with apps at scale and you have to make those choices top to bottom.
- vaughan 6y agoI feel like we are still waiting for someone to create a nice multi-paradigm database blending everything we’ve learned in the past 50 years, that can also run in the browser. I see all state as a stream of events building a graph, then we run queries on that graph. Then it’s all about optimizing the queries which we do. We’ve kind of shoehorned our use cases into whatever dbs we had available and have probably been overwhelmed by the speed we needed to scale our cloud storage resulting in sub-optimal solutions. Or maybe it’s just wishful thinking that there will exist a db to do it all.
- tyingq 6y agoAs an outsider to React, it seems significantly less batteries-included and more fragmented than Angular.