The Mulesoft app that synced Salesforce to Snowflake from a config list

A list of Sobjects and authentication details was all my Mulesoft app needed to sync data from Salesforce to Snowflake every hour (configurable) with the latest updates. Add a new object to the list or field to an existing Sobject, the app would see it and adjust the Snowflake data model accordingly.

I got it to the point that the initial seed of an object could handle hundreds of thousands of records in one batch. Obviously dependent on the records themselves, but the period of time retrieved each batch was configurable so I could make it work even for voluminous objects. There are enhancements I'd make to that architecture given hindsight.

I recently had to make that app more robust as it went from a tool to extract data for reporting to the tool that extracted all customer data from Salesforce to migrate to another CRM. Have I mentioned how cathartic those projects are and how valuable a seasoned expert is to include in that process? Anywho...

In the end, my Salesforce-Snowflake Mulesoft app supported even the wonkier objects to deal with in Salesforce- Content, Feed and History (but not ActivityHistory, that's not allowed). Credit where credit is due- Ryan McCloskey had already saved us with a solution that was syncing Salesforce files to AWS for that effort.

I'm going to be productizing some of the cool, general purpose solutions I've built over the years (they're always better the second time, with lessons learned and my propensity to extrapolate and make them more configurable). Any Mulesoft customers who could benefit from a solution like this? Steven Merlino, familiar use case you've heard?