The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. Monetization is currently on the rise, driven by the growing demand for APIs. With everything being provided as APIs nowadays, it's crucial to grasp this concept and establish a robust solution for subscription plans and the price model.
Vice President - Digital Integration at Kellton Tech Solutions Limited
Real User
Jun 3, 2021
On the API monetization side, being able to create separate consumption plans and throttle all those consumption plans towards the run time. Those are abilities that might need some improvements. The on-premises setup can be difficult.
Integration Analyst at a paper AND forest products with 5,001-10,000 employees
Real User
Mar 13, 2021
Some of the things that we use cannot be done in this solution. For these things, we have to either use a Java service or a util service. There is no predefined or existing service that we can use. So, we have to work on the util service and write on top of it. Its price can also be better. It is pretty costly because they charge us for each transmission.
webMethods.io is a robust integration platform offering seamless API management and business-to-business communications, enabling efficient workflows through a scalable and stable web-based interface.webMethods.io provides an extensive array of tools for efficient application integration, API lifecycle management, and secure business process automation. It supports various standards and protocols, ensuring flexibility for integrating both modern and legacy systems within hybrid or cloud...
The improvement needed is related to the model's position. As of now, it seems to be more of a conceptual idea rather than a widely implemented solution. Monetization is currently on the rise, driven by the growing demand for APIs. With everything being provided as APIs nowadays, it's crucial to grasp this concept and establish a robust solution for subscription plans and the price model.
On the API monetization side, being able to create separate consumption plans and throttle all those consumption plans towards the run time. Those are abilities that might need some improvements. The on-premises setup can be difficult.
Some of the things that we use cannot be done in this solution. For these things, we have to either use a Java service or a util service. There is no predefined or existing service that we can use. So, we have to work on the util service and write on top of it. Its price can also be better. It is pretty costly because they charge us for each transmission.