AWS AppSync vs TIBCO BusinessWorks comparison

"AWS has made it easy for developers like me to create and manage GraphQL APIs."

"Support for multiple data sources and formats is a fantastic feature."

"AWS has made it easy for developers like me to create and manage GraphQL APIs."

"Good TIBCO BusinessWorks features are the admin console and the ability to roll back to the previous version."

"It is very stable. It is a market leader, and it has connectors to many of the legacy systems. It also has enterprise cloud connectors."

"The most important thing is that it is easy for developers to work with."

"Good performance and reliability."

"The most valuable features are the stability and the time to market."

"One of the most valuable features is that it's a simple development. It takes a short time to get services to work."

"Customer support is very efficient."

"Drag and drop make it easier to build the service end to end."

"In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial."

"Moving to other clouds is impossible without significantly rearchitecting your applications."

"In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial."

"The communication protocols could be improved."

"Could be more user friendly in the development area."

"Performance and latency could be enhanced. Additionally, having signaling stack support would be beneficial."

"The creation of XSDs should be much simpler."

"The technical support's turnaround time is an area where TIBCO needs to consider improvements...Getting support from TIBCO on a particular issue takes a lot of turnaround time."

"The creation of XSDs should be much simpler. They should ensure that what was working in the previous version must also work in the new version of BW six."

"Its price can be improved. For medium enterprises, it is a very expensive tool. In the market, you won't get many resources for this solution. You won't find many developers in the market very easily. The latest version of TIBCO (6.4 or 6.x) is not very stable. It has got many issues. We have raised this with TIBCO, and they are taking a lot of time to come up with a fix, which is making us move away from this product. Some of the performance-tuning aspects are also missing in version 6. They should provide performance-related fixes, which will be helpful for the customers. If you are migrating from the current version to the container-supported version, it is quite expensive. The product has evolved, but it is very pricey. That's one of the challenges. They have provided all the features that are there in other products, but this is a platform upgrade. The platform has completely been changed from 5.x to 6.x, and we can't use the same environment. We can't run both versions on the same server as VM. The development environment is entirely different. In version 5.x, there was a proprietary designer. Now, it has common plug-ins developed on top of Eclipse."

"There are not many plugins available to integrate the databases. We have to write it in Java and integrate it. The developers should have more knowledge. These are the three main aspects that they could improve."

"Licensing fees are paid on a monthly basis, and it is a pay-as-you-go model."

"The solution is too expensive. It's one of the most expensive solutions out there, particularly because there are so many open-source competitors on the market. I don't know the exact numbers, however."

"I give the cost of the solution a four out of ten."

"TIBCO BusinessWorks is expensive."

"It is a bit expensive for medium-sized companies. If you are migrating from the current version to the container-supported version, it is quite expensive. The existing licensing will not work because the product platform itself is different."

"The payments made for service are the only addition to the standard licensing fees that we pay for the solution."

"I would rate the solution's pricing a three out of ten."

"Licensing scheme is too rigid"

"The cost depends on the components required."