We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.
I don't think webMethods is the cheapest but I think the quality is worth it. But it's not cheap. We're satisfied with our choice and the price is not a reason to look for something else.
Keeping in mind that we haven't explored the microservices completely, which has been a key element of their innovation recently, I do think webMethods is coming under increasing pressure when it comes to their price-to-feature value proposition. It's probably the single biggest strategic risk they have. They're very expensive in their industry. They've been raising the price recently, especially when compared with their competitors.
Currently, the licensing solution for this product is pretty straightforward. The way that Software AG has moved in their licensing agreements is very understandable. It is very easy for you to see where things land. Like most vendors today, they are transaction based. Therefore, just having a good understanding of how many transactions that you are doing a year would be very wise. Luckily, there are opportunities to work with the vendor to get a good understanding of how many transactions you have and what is the right limit for you to fall under. With any solution like this, on day one you have a project that you're trying to work on, but just understand where you are trying to go with the solution. Some plugins are cheaper than others, and others are more expensive than others. Just make sure that you understand the full scope of what you might end up using the product for, so you can understand the all-in costs. The tool works extremely well. Software AG offers packaged solutions for many packaged apps. Oracle SQL Server or Salesforce are add-ons that you can purchase and install easily for plug and play with packaged solutions. When you start moving into custom applications, there are no packaged solutions. The good news is that typically custom apps are built in some type of known technology, and that technology can easily be integrated into webMethods Integration Servers. Business-to-business communications is an add-on that needs to be purchased. While super important to my organization, it is an add-on outside of the standard webMethods Integration Server. I would strongly recommend the business-to-business add-ons, especially if you're looking to use webMethods Integration Server in that capacity. It just makes the development cycles a lot shorter as well as making it much easier to manage your business profiles.
It's a good deal for the money that we pay.
This is an expensive product and we may replace it with something more reasonably priced.
The vendor is flexible with respect to pricing.
The pricing and licensing costs for webMethods are very high, which is the only reason that we might switch to another product.
It is expensive, but we reached a good agreement with the company. It is still a little bit expensive, but we got a better deal than the previous one.
I suppose webMethods aim for large-scale enterprises which is why the price is high, but with high output and better outcomes. Some of the licensing is "component-ized," which is confusing to new users/customers. Yet you can also choose between perpetual or periodically terms, in case you do not want to be bothered to buy another version once the newer version released you should consider periodic license.
Hi, I'm working at a consulting company and I want to understand the pros and the cons of Red Hat Fuse vs webMethods Integration Server.
I am looking for few suggestions on key focus elements while evaluating ESBs with consideration to the services that will be accessing Big Data.
Your ideas are much awaited and appreciated.