I'm a full stack Typescript developer specialising in Angular and Node. I love reactive programming with RxJS, utilising the less-used web APIs and I'm passionate about polymorphic full stack TS.
Hmm interesting thought - you’d have to be very careful about how you split the work - for example splitting the store so that each worker is only working on part of the store that any action would only affect that slice of state. I’d be quite dubious of the performance cost though as state transfer and re-merging is probably comparable to the actual reducer cost.
What could be done which would be interesting is offloading all effects to parallel webworkers and keeping the reducers on the main thread. I think this would be a really nice pattern if the effect functions were computationally intensive
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article! Crazy idea... but do you think you could split a redux stores reduces to be processed by multiple workers?
webWorkerAllTheThings
Hmm interesting thought - you’d have to be very careful about how you split the work - for example splitting the store so that each worker is only working on part of the store that any action would only affect that slice of state. I’d be quite dubious of the performance cost though as state transfer and re-merging is probably comparable to the actual reducer cost.
What could be done which would be interesting is offloading all effects to parallel webworkers and keeping the reducers on the main thread. I think this would be a really nice pattern if the effect functions were computationally intensive