Screw DataStage
Screw Saleforce
Screw the $25k/week Vendor who finishes work maybe 60% complete, if I’m being generous.
Screw the business rushing to us to fix their shadow IT cluster.

Skrew Salesforce?

I'm intrigued!

@C0D4 ETL from on premise databases to SF via DS. I have zero control of SF as “that’s the business’ purchase”. Because they want the ETL to write to the objects behind the Lightning UI, SF’s Process Builder must be manually turned off for the ETL to run at a decent time.

@bkwilliams I'd swap out the PB's into apex triggers, you get a bit more control over execution where as PB's tend to be slow and timeout in bulk processors like ETL or bulk processing.

@C0D4 thanks! However the business has 100% control of the SF pods, so all I can do is recommend changes.

@bkwilliams ah, that sucks.
. I'm assuming they follow the config before code mantra too?

We use to do this, but we had a massive refactor last year to bring ourselves back down to meet governance limits and timeouts due to introducing a 3rd party vendors packages - they be slow 🤦‍♂️

Ajay's comment sums it up.
https://developer.salesforce.com/fo...

You do eventually hit a point that a pb can't keep up and becomes the bottleneck, that's the perfect time to scrap it and swap it for triggers. Just being able to access before/after update/insert alone is beneficial as it changes the way you can implement things.

For minor updates, a pb is still acceptable though and will work.