RapidAPI vs. WSO2 API Manager

I always used and develop API with RapidAPI so also recommend to new people to use and learn about APIs. If we discuss about new user it's so easy to learn and develop API free of cost as well as paid subscription. My experience with RapidAPI is awesome.

It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?

Incentivized

• API uptime and scalability i trusted the most.
• API design is so easy even new person can easily develop API at there.
• Support every type of API like REST, SOAP etc.
• Very easy workflow

• Authentication based on OAuth 2.0 and HTTP Basic Authentication.
• Rate Limiting applied at different levels like Subscriber, API, Resource and Backend.
• Monitoring by exporting the metrics in Prometheus and traces in Jaeger.
• Mediation to perform transformation, orchestration etc.

Incentivized

• Little issue for new user while designing new API through user interface of RapidAPI.
• Not sure about the security of the API so not possible for prodcution mode.

• Better QA testing prior to releases rollout
• Better support needed

Incentivized

Firebase is also good tools for user who are working on APIs but the marketplace of Rapid API is non comparative. Like how it's creates APIs and testing phase, supporting of multiple API types etc. These features makes Rapid API very unique from else ones.

Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.

Incentivized

• Front-end Devs like me not want to invest money for back-end so Rapid API is best option to try and design API's in very easy way.
• In case of using the more of Rapid API we can take subscription which is also on nominal prices.
• For front-end devs not need to learn back-end skills in Rapid API.

• We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
• Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
• Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.

Incentivized