Jitterbit vs. Swagger Open Source, supported by SmartBear

Small to medium sized companies are great prospects for this product. It's pretty easy to set up, learn and maintain. You can scale it too, so start with an easy integration, learn the ropes and expand your usage. If you have fairly simply needs for a handful of fields and just one or two external systems to feed into Salesforce, this is the go-to product. If you're a larger company needing more complex integrations where extremely high reliability is needed and any downtime means revenue loss, you probably already have a different product in mind. Then again, you probably have an entire team that handles integrations and a data warehouse to support it!

Incentivized

To my opinion Swagger Open Source is a very good tool to quickly produce an api documentation, that how I use it.Swagger can also produce an open api file to generate an api for our application server (Inersystems Iris) but we don't use this functionality for now. We plan to use more Swagger features in the future.

Incentivized

• Ease of use - while being more technical is useful, you don't need to be a developer to use many of JItterbit's capabilities
• Customer Support - we have always had great responsiveness to any questions or issues encountered
• Reliability - Jitterbit has been extremely reliable with no major outages in the recent past

Incentivized

• Produce documentation
• user interface to create api definition
• reusability of data description

Incentivized

• Some of the more advanced transformation possibilities aren't exactly clear without a lot of digging. Very basic connections (e.g. map this field to this field) along with basic transformation scripts (e.g. multiply X * Y) are super easy. But I know there are a ton more features and functionality that I feel is somewhat buried in the product

Incentivized

• for me the UI can be more simple
• too many functionnalities when just want to produce doc, can be a separate app
• A french documentation will be apreciated

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

Hands down, Jitterbit is more cost-effective than Informatica, either on-prem or cloud and the value only goes up from there. Reusability and ease of creation make in-house training simple and the end result is we leverage Jitterbit for much more than what we initially considered it for. Having used Oracle and TIBCO before as well, I find they are the tools of yesterday, not able to keep up in terms of functionality or price. Mulesoft would be a more relevant comparison, and I feel we lean on Mule far more than Jitterbit, but both tools have their place and their strengths (and weaknesses!).

Incentivized

We use swagger only to generate the API documentation, for testing the APIs, we use Postman. We don't find an other tools for producing API documentation in web pages and also in pdf files. Postman is a good complement for testing APIs on InterSystems IRIS (a powerful application server and DB manager) which implements these APIs.

Incentivized

• We moved from a product that was failing regularly (jobs were running long, some jobs would finish incomplete without any warning or info, etc) to Jitterbit - a very stable product if you give it the recommended server size it needs.
• It has made crafting solutions for data movement and transformation quick!

Incentivized

• Less time to produce our documentation
• Documentation can be accessed online, this is a plus for our customers and partners
• Great tools to communicate with other project actors

Incentivized