AWS Service Broker vs. Jitterbit

AWS service broker is best if your company uses AWS as Cloud provide and your company wants to minimize the efforts for integration with third-party software then AWS service broker is best to use. It gives a convenient to operate third-party software from the comfort of the platform itself.

Incentivized

This is a great tool for bringing data out of your locked, internal systems and getting it into the cloud. It meshes well with Salesforce and is fairly easy to use, helping the transition from other older, more complex tools into a more modern environment. It has lots of competition in this space and some are better than others, but if your data is straight forward and you know it well, Jitterbit will get the job done. If you are not as close or comfortable with your data and need to do some wildly complex migrations, there might be better packages out there for you.

Incentivized

• Integration with third party software like VMware
• Clear Instructions and documentation
• Customized templated for easy deployment

Incentivized

• UI is super easy to understand with a low learning curve so admins can figure it out and maintain it without breaking anything.
• It's FREE! There's a paid version too but I like that you can use most of the features for free and they're not pushy with buying.
• There's a great user community that you can google and ask any questions. Most problems I've encountered have been posted and answered already.

Incentivized

• Integration with third party application are limited
• Give an option for details underlying implementation
• Hard to manage at first

Incentivized

• Migrating operations from QA to Production work well for initial deployment, however, when migrating an update to an existing job to production, sometimes certain project items are duplicated. This is not the end of the world... the duplicates can be removed, but would be nice if it was not required.
• I have not found a way to trap under-the-covers SOAP errors (for example, when a query you are running against Salesforce takes too long). You get a warning error in the operation log that the job only pulled a "partial" file, but it does not fail.

Incentivized

I have been evaluating other tools as a continuous improvement practice. I would like something that would be easier to use for a non-technical user. I work for a small organization and have no back-up for Jitterbit if something happens to me. We don't have the technically savvy employees to understand it.

They have some of the best support of any software vendor that we use. They always get our issues resolved quickly

It provides more easy and convenient integration with third-party software. you can simply operate any third-party software like VMware from the platform itself which is not provided by Azure App Service. Although other services are the same I recommend using AWS service Broker against any other service providers.

Incentivized

Evaluated Dell Boomi and Celigo as alternatives prior to purchasing Jitterbit. We went with Jitterbit at that time because we could handle all changes ourselves without any assistance from Jitterbit, and we liked their size and nimbleness. Dell Boomi was too big for us, and Celigo at that time did not have a self-service model. Every change had to go through them (although that has since changed). We were not in a position to be able to wait for someone to make changes for us given the rate of change within the business.

Incentivized

• less spend on Integration
• overall positive Impact
• More productivity

Incentivized

• The time it takes to connect systems has reduced by orders of magnitude. Previously, we would custom-develop connectors between various systems and they would all be managed by different vendors. With Jitterbit speed-to-deploy and the efficiency gained by managing all connections in one dashboard has been the greatest piece of the ROI.

Incentivized