4 ms·

I'd say that having a (buggy) in house integration with Salesforce is a way bigger tech debt than using AppFlow here. If one day you want to move off Salesforc

I'd say that having a (buggy) in house integration with Salesforce is a way bigger tech debt than using AppFlow here. If one day you want to move off Salesforce to another service, you will just switch off the configuration in AppFlow for the new service. Sure you're locked in AWS, but it takes tech debt away from other things, plus might save you migration costs.

nicoburns 7y ago
> I'd say that having a (buggy) in house integration with Salesforce is a way bigger tech debt than using AppFlow here. That assumes that the AppFlow code is not buggy. In my experience these services are very hit and miss. This might be a good one, but it's impossible to tell until you use it (or read experience reports of others using it). Reliable 3rd party services can be a big time saver, but Unreliable/Buggy/Limited 3rd party services can easily take 5x more time than something in-house.
- aledalgrande 7y ago
  I'd gander that an AWS team would be more capable than your average startup team. And testing if AppFlow works for you will take way less than building your own.
pydry 7y ago
I'd say that: * About 70-80% of what you want to do with a service like appflow to integrate with a service like salesforce will be possible. The other 20-30% of your requirements will require building a bugging in house integration from the ground up. Might as well start off that way. * As soon as you hit a wall with a service like appflow that is usually it. You'll raise a ticket and be stuck until they get around to implementing it. There are fewer roadblocks with home grown implementations of integrations.
- aledalgrande 7y ago
  Not saying it will work for all cases, but a majority of integrations are pretty basic. I have done a few. Usually just data mangling between different systems, which is exact what AppFlow is good for. Also if you are on a business plan, the response time is pretty good. I got feature requests done in Sagemaker.

nicoburns 7y ago

> I'd say that having a (buggy) in house integration with Salesforce is a way bigger tech debt than using AppFlow here. That assumes that the AppFlow code is not buggy. In my experience these services are very hit and miss. This might be a good one, but it's impossible to tell until you use it (or read experience reports of others using it). Reliable 3rd party services can be a big time saver, but Unreliable/Buggy/Limited 3rd party services can easily take 5x more time than something in-house.

aledalgrande 7y ago
I'd gander that an AWS team would be more capable than your average startup team. And testing if AppFlow works for you will take way less than building your own.

pydry 7y ago

I'd say that: * About 70-80% of what you want to do with a service like appflow to integrate with a service like salesforce will be possible. The other 20-30% of your requirements will require building a bugging in house integration from the ground up. Might as well start off that way. * As soon as you hit a wall with a service like appflow that is usually it. You'll raise a ticket and be stuck until they get around to implementing it. There are fewer roadblocks with home grown implementations of integrations.

aledalgrande 7y ago
Not saying it will work for all cases, but a majority of integrations are pretty basic. I have done a few. Usually just data mangling between different systems, which is exact what AppFlow is good for. Also if you are on a business plan, the response time is pretty good. I got feature requests done in Sagemaker.