Jitterbit is a cloud integration technology for cloud, social or mobile apps. It provides accessibility for
non-technical users, including easily creating API’s and data transformation scripts within the
integrations.
$1,000
per month
TIBCO Messaging
Score 7.7 out of 10
N/A
TIBCO offers high-performance messaging technology, and gives customers flexibility and unique choice between Commercial and Open-source messaging solutions. TIBCO Messaging is a comprehensive messaging portfolio available to meet a wide variety of use cases and deployment models.
N/A
Pricing
Jitterbit
TIBCO Messaging
Editions & Modules
Jitterbit
$100.00
Starting Price Per Month
No answers on this topic
Offerings
Pricing Offerings
Jitterbit
TIBCO Messaging
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Jitterbit
TIBCO Messaging
Features
Jitterbit
TIBCO Messaging
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
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.
Organization which uses TIBCO Business Works or TIBCO Business Process Management or TIBCO BPM Enterprise can make use of TIBCO Messaging as it works well with other TIBCO tools. Many TIBCO tools have TIBCO Messaging products bundled as a package along with other TIBCO tools. Use of dynamic topics and queues makes run time processing easier.
Tibco EMS performs very well, and it meets our stringent performance requirements for corporate messaging backbone.
Tibco EMS scales well, and this is another of our stringent requirements.
Tibco provides good support for the EMS product, and continues to improve it. This is important as we don't want to use something that does not keep up with the changes in the technology landscape.
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.
In terms of TIBCO Messaging, it would nice to have a more out-of-the-box way of linking its objects (queues, topics) directly to those of other popular solutions like MQ or Kafka.
Not being able to filter (that is, using selectors) through patterns/subtexts on the message body is missed on occasions.
Given the current trends and state-of-art, lift & shift of on-premise EMS clusters to cloud architectures should be more directly attainable.
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.
EMS is a solid system and I see no reason to abandon it, in fact I am eager to see what the next versions will offer and future road maps. Knowing we have support to help us in case of problems is invaluable, both in case of critical issues and to improve overall performance.
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.
We also use other messaging products: IBM MQ, especially for integration with other systems (server2server), which has been an industry standard for a long time, and Apache Kafka for cloud-native applications. EMS is a worse option compared to them, but it is still acceptable.
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.
