3 ms·

And nothing of value was lost. God, I hate everything about Salesforce. Sometimes I have to integrate against their services, and it is always a pain, not to me

by jtrn 10d ago

And nothing of value was lost. God, I hate everything about Salesforce. Sometimes I have to integrate against their services, and it is always a pain, not to mention what the core project actually is: optimization of marketing and spam.

chasd00 10d ago
not really defending salesforce but OAuth+REST is a pain? Pretty plain vanilla in terms of integration requirements.
dd8601fn 10d ago
Sure, if you’re struggling with weird custom endpoint behavior, or custom triggers and validation, that’s on your admins and devs. But if you’re having trouble with the standard rest or bulk apis, that’s 100% on you.
- jtrn 9d ago
  If you think integration with Salesforce = REST API then you have no idea what you are talking about.
felineflock 10d ago
What is painful about a plain REST API?
- jtrn 9d ago
  A normal sensible REST api ? Nothing. Salesforce API? Sandboxes drift from production in both metadata and data. Refreshes change record ids. API access is gated by edition. Professional edition has none by default. Salesforce sells MuleSoft as the fix to their own shit architecture. Custom objects and fields mean that connecting successfully doesn’t establish what represents a customer, subscription or completed sale. Even standard objects can be used differently between organizations. Metadata deployment is SOAP-based and slow. Dependencies between components break deploys and is massive pain to debug. And notice that I said integration, not API integration. There’s a shit storm of terrible way to integrate beyond just simple API. Have fun with Bulk 1 or 2, Composite, Streaming, Platform Events, Change Data Capture, Tooling, GraphQL. An my most hated item, anything web based. I seriously want to talk to someone that have a good time integrating against Salesforce. Maybe I will have my mind blown as to how easy it could be, but I suspect I will have the same experience I have every time I critical scrutinize and such situation: it’s just as terrible as it seems and the person claiming it’s easy is hands down producing close to nothing of value.

by jtrn 10d ago

chasd00 10d ago

not really defending salesforce but OAuth+REST is a pain? Pretty plain vanilla in terms of integration requirements.

dd8601fn 10d ago

Sure, if you’re struggling with weird custom endpoint behavior, or custom triggers and validation, that’s on your admins and devs. But if you’re having trouble with the standard rest or bulk apis, that’s 100% on you.

jtrn 9d ago
If you think integration with Salesforce = REST API then you have no idea what you are talking about.

felineflock 10d ago

What is painful about a plain REST API?

jtrn 9d ago
A normal sensible REST api ? Nothing. Salesforce API? Sandboxes drift from production in both metadata and data. Refreshes change record ids. API access is gated by edition. Professional edition has none by default. Salesforce sells MuleSoft as the fix to their own shit architecture. Custom objects and fields mean that connecting successfully doesn’t establish what represents a customer, subscription or completed sale. Even standard objects can be used differently between organizations. Metadata deployment is SOAP-based and slow. Dependencies between components break deploys and is massive pain to debug. And notice that I said integration, not API integration. There’s a shit storm of terrible way to integrate beyond just simple API. Have fun with Bulk 1 or 2, Composite, Streaming, Platform Events, Change Data Capture, Tooling, GraphQL. An my most hated item, anything web based. I seriously want to talk to someone that have a good time integrating against Salesforce. Maybe I will have my mind blown as to how easy it could be, but I suspect I will have the same experience I have every time I critical scrutinize and such situation: it’s just as terrible as it seems and the person claiming it’s easy is hands down producing close to nothing of value.