These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
EventsourcedWriter) with ConditionalRequests. BUT: you have to deal with ConcurrentVersions - so you MUST detect and merge duplicated generated UIDs for the same external data, "Last-Writer-Wins" strategy is not an option for this topic.
About the performance... i have been working almost five years in Android development, and i have the opinion that most mobile apps perform poorly (for what could already be done nowadays), but we got used to consider that amount of wait times acceptable :D. It is also true that modern smartphones are fast and can do moderately complex things in a good enough time, but there are also markets with low end smartphones that perform many times slower and have very little memory. In that scenarios some apparently trivial optimizations can mean a lot...
The design you suggest seem interesting to me for content/data generated from user actions received at the application service and i could use it for similar things later on. But the part i am currently focused in where data comes from parsing external systems and the user actions just lead to queries on the processed data does not seem to fit on it too well because the IDs need to be created / queried well before the application layer knows anything about that data.