Reverse is only meaningful when you're used to a specific view that ETL can only load into a single destination. (Usually data warehouse)
Just like the term "push notification" which are a specific kind of communication from the server to a mobile device but in fine, it's the device calling a service to know if there are any notification waiting for them. A Message Queue in other words...
The differentiation in terminology is entirely a fiction created by marketing teams for these kinds of tools.
I'm saying this is someone that sees the benefit in this specific tool and desires to implement it for my team.
There is no reason that tools like FiveTran couldn't handle the same things that tools like Census do. They just focused on a specific set of use cases, ignored other ones that were more of a paradigm shift. Then when teams created products that fill this void they referred to them as reverse ETL for entirely marketing reasons.
It's an example of where enterprise software gatekeepers such as Gartner drive negative value by deliberately confusing the language to sell their magic quadrant reports to risk adverse executives at massive corporations.
Have you considered adding source connectors for S3 based data lakes? For example Parquet files or Delta Lake? Maybe via AWS Athena to make it similar to the Red Shift connector?
https://github.com/orgs/Multiwoven/projects/4/views/1?pane=i...
When you push data into Salesforce, and Salesforce (API) returns error messages indicating some row in the target can't be modified because it is busy, is your tool able to detect which rows couldn't get loaded and retry those rows N times (hopefully with some exponential backoff delay or perhaps a fixed delay between retries), and then if those retries fail, report back up permanent failures of which rows/IDs didn't make it to Salesforce? (I haven't run across a tool that does this but this was my pain point.)
https://join.slack.com/t/multiwoven/shared_invite/zt-2bnjye2...
