3 ms·
You absolutely do have to use Lambda to integrate your call center with Salesforce. Your call center agents use their familiar Salesforce screen when a custome
by scarface_74 3y ago
You absolutely do have to use Lambda to integrate your call center with Salesforce. Your call center agents use their familiar Salesforce screen when a customer calls in.
But you’re so concerned with “cloud lock in” and you completely ignore the other 200+ services that the average enterprise is using. Why are you so concerned with the cloud, but not Salesforce, ServiceNow, Sharepoint, Okta, Azure AD, etc?
It makes no technical sense to spend developer time and add complexity to create an ETL job to do what a simple SQL statement can do.
None of this is “making the beer taste better”.
I’ve shared by credentials up thread - 2 years heading a migration and integration when a private equity owned health care company was acquiring companies to get big and go public, 3 years leading the application modernization effort for another company that was acquired at 10x revenue and three years working at AWS in the Professional Services department and now building out a professional services practice for an MSP for applications modernization.
And before that over 20 years as a professional developer
- zmgsabst 3y agoThere is no technical requirement to use a Lambda to integrate Salesforce — feel free to cite contrary information. https://help.salesforce.com/s/articleView?id=sf.integrate_what_is_api.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.integrate_wh... > But you’re so concerned with “cloud lock in” and you completely ignore the other 200+ services that the average enterprise is using. Why are you so concerned with the cloud, but not Salesforce, ServiceNow, Sharepoint, Okta, Azure AD, etc? This is a fantasy you invented about me because you cannot respond to my actual point — a strawman. My original advice was to use the cloud — and I was addressing someone else’s concern about lock-in, while giving advice that would aid their initial migration to using cloud services. I think that it’s very telling you can’t be honest about what I said. > It makes no technical sense to spend developer time and add complexity to create an ETL job to do what a simple SQL statement can do. As is this — another strawman you invented. - - - - Why do you have two strawmen, but haven’t in several posts actually addressed my specific example? Are you unable to? - - - - What you’ve said is that you spent two years migrating just a hundred VMs, which sounds like a migration delayed by self-induced complexity. I appreciate arrogantly incompetent developers like yourself — who can’t address technical points and instead resort to fallacious thinking: Your work gets me paid.
- scarface_74 3y agoYou did see the part about integrating Salesforce with a Connect call center didn’t you? So I’m an “incompetent developer” who someone managed to get hired at AWS Professional Services not a third party partner - you to consult the largest organizations on the planet? I’m sure an AbstractFactoryRepositoryFacade is going to prevent cloud lock-in while you advise people to create a complicated workflow when a simple SQL statement using an AWS extension would be faster to develop, more performant and less maintenance? It’s not a straw man it goes to the core of the efficiency gains you get by taking advantage of your vendors functionality and integrating into it tightly instead of trying to maintain a leaky abstraction.
- deleted 3y ago[deleted]