GNU Make vs. Jitterbit

Makefiles are machine-readable documentation that make your workflow reproducible. If the build process is a very continuous flow of operations within scope, it will do it well and also act as a documentation of all the dependence. For some long-term projects, Make has been used extensively and being maintained to do the job.

Incentivized

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

• Performance and accuracy of cross-module dependencies.
• Simple to write and easy to understand.

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

• No dependency management tools (but there are no cross-platform tools of this type anyway)
• Tedious to do cross-compilation (Debug & Release builds, 32- and 64-bit builds, x86/ARM builds)

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

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.

In general, it is fair to say the support is sufficient although we do not deal with support directly. There are a lot of forum people chiming in with suggestions or recommendations of particular usage or issues we run into. Since it is open software, patch and fixes will be available from time to time. A lot of information is available in the web now for knowing GNU Make from learning, example, teaching, etc.

Incentivized

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

I'm a full-stack developer that has used various build tools, including Maven, Gradle, and NPM/yarn. For our C projects, I also investigated CMake and Ninja, but they seemed more difficult to learn and more tedious to work with. GNU Make is a single binary that can be easily downloaded, even for Windows under MingW32, is straightforward to learn, and works pretty well despite its age.

Incentivized

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

• Easier to onboard new developers
• Straightforward integration with CI/CD systems

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