kunalrgarg

5 ms·

1. 1.▲
   by kunalrgarg 3y ago

   I haven’t heard of Valadic, but I’ll definitely check it out. Thanks for flagging!
2. 2.▲
   by kunalrgarg 3y ago

   Wow congrats on making it through with CometD and Bayeux. I think salesforce has realized that a lot of their APIs aren’t useful when using non standard approaches. I think the move from SOAP to also including REST was a signal that they’re
3. 3.▲
   by kunalrgarg 3y ago

   Yeah definitely agree, we had to rework our logic for these cases. We've worked with ~4 Million row objects. In general with our polling strategy syncs, the problem was more the size of each record. So a table with 1M rows but 400 fiel
4. 4.▲
   by kunalrgarg 3y ago

   Yeah, so far, we’ve found that this combination of the three APIs is a happy medium between reliability, simplicity, and API limit consciousness.
5. 5.▲
   by kunalrgarg 3y ago

   That's awesome that you set this up, thanks for paving the way! Our users who want real-time syncs and are watchful of their REST API limits typically opt in for our streaming solution (I believe the pub/sub api was a recent addit
6. 6.▲
   by kunalrgarg 3y ago

   Thank you! We’re primarily a TypeScript team with Next/Nest frameworks on GCP, using serverless where we can
7. 7.▲
   by kunalrgarg 3y ago

   Yes, you’re correct on that! Sorry for the lack of clarity on the docs. The snapshots would be stored in a client side table in these cases. These snapshot tables/collections can either be stored in your own PG or MongoDB.