Hi @rahul,
Many thanks for raising the request and apologies for the delay replying. We’ve had this ticket for a while. However, we haven’t had many people make the request for mobile specifically - if anything, we’ve had lots of people ask us to implement downstream technology (e.g. relays) to save:
- More SDK bloat in the apps themselves
- Reduce the network traffic coming off the mobile app
Just to confirm - (2) doesn’t seem to be a concern in your case?
Can I be a bit nosey - can you share any more about where the requirement comes from i.e. why do you want to send some data to a batch pipeline and some to a real-time pipeline? Would having a single real-time pipeline and then a micro-service that triages the data (e.g. that reads the enriched stream and writes out to different downstream streams) be preferable, both in terms of simplifying the the mobile implementation, and consolidating your data processing infrastructure?
I want to make sure we understand the context of the requirement as well as possible before diving into the best updates to make to the stack to support them.
Thanks!
Yali