Azure CDN vs. Stoplight vs. SwaggerHub

Azure CDN has at hand an infinity of applications and tools to implement in your system and have better control of your data in a clean and secure platform on the web, we recommend this program since the percentage of solutions provided by this program is very high and find a way to make each user's job easier.

Incentivized

API mocking, testing, and sharing are all built in functions for StopLight that work quite well. They even have functionality for generating OAI and RAML code as well, which is a huge plus. AS for as areas where StopLight is not appropriate, if you're doing anything other than API testing, StopLight may not be appropriate for use.

Incentivized

ReadyAPI and SwaggerHub are a match made in heaven. Being able to so easily import the API directly into ReadyAPI and then being able to generate a test suite from the API is my favorite part of these softwares. We have rather large services so building out the API can take some time

Incentivized

• I found the CDN very easy to setup and configure within the Azure Portal.
• Being Azure, there are plenty of free tools that allow you to manage the CDN from a UI that is not the portal. This was especially handy when I trained end users how to manage content within their specific realm.

Incentivized

• OpenAPI support
• Markdown supports
• Git integration

Incentivized

• Treating the design as documentation ensures that we have consistent and well defined APIs
• API consumers can export the swagger definition or code stubs to use within their development environment
• We can iterate through multiple versions of a definition privately before making a version publicly available

Incentivized

• Tough learning curve--you have to be comfortable with the Azure Cloud logic and UI to use it easily
• Special or uncommon use cases' pricing can be hard to forecast/follow
• Can be expensive for simple use cases

Incentivized

• Simplicity of set up. Although it's not difficult, there are tools out there that are easier to set up for testing endpoints.
• Again, it's perfectly functional, but some competitors I think have a more user friendly UI to them.

Incentivized

• The user interface could be more improved to sustain with other similar tools in the market.
• Beneficial if we have better integration with third party softwares.
• Nice to have ability to download the documentation in usable formats.

Incentivized

I give it 9/10 rating because it solved my problem by Caching my website content on global servers to load faster.

Great support from the team whenever we're stuck. Very proactive in resolving issues and also making changes as per the requirements of the organization.

Incentivized

More user friendly and it’s so easy to learn, the prices may be close to each other, but the service is excellent.

Incentivized

I'd like to also throw Runscope and Fiddler into the mix. Between StopLight and all these competitors, we've chosen StopLight primarily for the support, ease of use, and reliability. Most tools out there today are top-notch, so it really comes down to personal preference and different use-cases. Having used other API testing frameworks, StopLight definitely stacks up against the competition.

Incentivized

The only other product we looked at was Postman. But we liked the SwaggerHub UI & the integrations it has with the AWS API gateway. Though Postman has some other great features like the ability to write test cases & execute them, SwaggerUI was more convenient to document & share them.

Incentivized

• Azure CDN reduced origin instance load by removing the need to constantly serve large numbers of static files, meaning applications can be deployed with smaller/fewer instances.
• Azure CDN reduces apparent load times to customers by serving cached files out of POPs in the local region of those clients, instead of requiring those clients to make multiple, lengthy requests through to the origin servers.

Incentivized

• Increased efficiency
• Improved comminication between backeend and frontend

Incentivized

• Faster API development lifecycle.
• Reduced discussion time when building a new vital API endpoint.
• Complete documentation which makes the new team member onboarding process easier.

Incentivized