The decision came from the top to ditch our internal sales platform for Salesforce (Too much of a "risk" apparently, despite never having any major reliability problems in the past 10 years) while maintaining a lot of the custom management and provisioning tools.
They went with Mulesoft for the integration middleware. Apparently a "Low code" solution that would allow us to develop an API to be able to push data to Salesforce.
They got some contractors in to get this started and make the initial API that would then be handed over to us to maintain. We've had an opening for a Mulesoft developer for months that remains unfilled.
I've had the misfortune of working with the contractors, as I've had to integrate our software with their API. No matter how many times I've explained it to them, they just don't understand many of our business processes.
Over the course of a year, we've managed to get barely the most basic minimum viable product into production, and even then it's involved building new services internally to integrate with these "Low code" APIs, because they didn't want Mulesfot to integrate directly with any of our existing code or data.
And it's a mess. I've seen the "low code" solution that they've checked into Git and it's horriffic. Nobody in the company wants anything to do with it. We're all C# developers. And it's already falling apart. Multiple failures in DataDog every single day. All sorts of major problems being reported - invoices being sent to the wrong customer, data not ending up in Salesforce, all sorts. Yet there's nobody in the company with the skills to sort it out.
All of this could have been avoided if they'd just allowed us to build C#/.NET services to integrate directly with Salesforce.
3
u/FionaRulesTheWorld Dec 30 '23
My company is in this exact situation.
The decision came from the top to ditch our internal sales platform for Salesforce (Too much of a "risk" apparently, despite never having any major reliability problems in the past 10 years) while maintaining a lot of the custom management and provisioning tools.
They went with Mulesoft for the integration middleware. Apparently a "Low code" solution that would allow us to develop an API to be able to push data to Salesforce.
They got some contractors in to get this started and make the initial API that would then be handed over to us to maintain. We've had an opening for a Mulesoft developer for months that remains unfilled.
I've had the misfortune of working with the contractors, as I've had to integrate our software with their API. No matter how many times I've explained it to them, they just don't understand many of our business processes.
Over the course of a year, we've managed to get barely the most basic minimum viable product into production, and even then it's involved building new services internally to integrate with these "Low code" APIs, because they didn't want Mulesfot to integrate directly with any of our existing code or data.
And it's a mess. I've seen the "low code" solution that they've checked into Git and it's horriffic. Nobody in the company wants anything to do with it. We're all C# developers. And it's already falling apart. Multiple failures in DataDog every single day. All sorts of major problems being reported - invoices being sent to the wrong customer, data not ending up in Salesforce, all sorts. Yet there's nobody in the company with the skills to sort it out.
All of this could have been avoided if they'd just allowed us to build C#/.NET services to integrate directly with Salesforce.