Alex D

@SaltedBlowfish It can cache data in memory and provide to components, before writing to db. And pls lets post here if you fully understand the question and watermelon architecture.

@KrisLau you don't understand the question.

@SaltedBlowfish ok lets ask differently: 1) does it manage some in-memory cache? 2) when do observers receive changes - before actual write to database or after? First is much faster....

1) It actually does, but only for getting entities by id. Which is definitely not enough for making a fast app. 2) This is very bad for performance either. 3)...

@Albert-Gao before giving such advices you better learn how to build high performance client apps first, or just study some client app architecture basics at least. And I would never...

Why not to add useEntity also? const entity = useEntity(`User:${id}`)

@danReynolds for performance it is much more inefficient to map entity into fragment, I guess problem here could be with proper typing in typescript.

When downgraded Xcode to 13.2.1 it started showing another issue: > ld: building for iOS Simulator, but linking in dylib built for iOS, file '/Users/main/Projects/work/PerksApp/ios/Pods/AgoraRtm_iOS/AgoraRtmKit.framework/AgoraRtmKit' for architecture arm64

@Godzilla912 this issue is for `agora-react-native-rtm` package, not flutter.

Persisting separate reducers fixes that, so each reducer state is serialized separately. But how to serialise each value in reducer state separately is a question I'm searching answer for.