Azure API Management vs. Red Hat JBoss Enterprise Application Platform

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure API Management
Score 7.8 out of 10
N/A
Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
Red Hat JBoss EAP
Score 7.9 out of 10
N/A
N/AN/A
Pricing
Azure API ManagementRed Hat JBoss Enterprise Application Platform
Editions & Modules
Consumption
0.042 per 10,000 calls
Lightweight and serverless version of API Management service, billed per execution
Developer
$48.04
per month Non-production use cases and evaluations
Basic
$147.17
per month Entry-level production use cases
Standard
$686.72
per month Medium-volume production use cases
Premium
$2,795.17
per month High-volume or enterprise production use cases
Isolated
TBA
per month Enterprise production use cases requiring high degree of isolation
No answers on this topic
Offerings
Pricing Offerings
Azure API ManagementRed Hat JBoss EAP
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Azure API ManagementRed Hat JBoss Enterprise Application Platform
Top Pros
Top Cons
Features
Azure API ManagementRed Hat JBoss Enterprise Application Platform
API Management
Comparison of API Management features of Product A and Product B
Azure API Management
8.0
4 Ratings
1% below category average
Red Hat JBoss Enterprise Application Platform
-
Ratings
API access control8.94 Ratings00 Ratings
Rate limits and usage policies5.44 Ratings00 Ratings
API usage data8.94 Ratings00 Ratings
API user onboarding9.03 Ratings00 Ratings
API versioning8.94 Ratings00 Ratings
Usage billing and payments5.23 Ratings00 Ratings
API monitoring and logging9.84 Ratings00 Ratings
Application Servers
Comparison of Application Servers features of Product A and Product B
Azure API Management
-
Ratings
Red Hat JBoss Enterprise Application Platform
8.6
8 Ratings
8% above category average
IDE support00 Ratings8.18 Ratings
Security management00 Ratings8.68 Ratings
Administration and management00 Ratings8.18 Ratings
Application server performance00 Ratings8.68 Ratings
Installation00 Ratings9.58 Ratings
Open-source standards compliance00 Ratings8.68 Ratings
Best Alternatives
Azure API ManagementRed Hat JBoss Enterprise Application Platform
Small Businesses
NGINX
NGINX
Score 9.1 out of 10
NGINX
NGINX
Score 9.1 out of 10
Medium-sized Companies
NGINX
NGINX
Score 9.1 out of 10
NGINX
NGINX
Score 9.1 out of 10
Enterprises
NGINX
NGINX
Score 9.1 out of 10
NGINX
NGINX
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Azure API ManagementRed Hat JBoss Enterprise Application Platform
Likelihood to Recommend
8.0
(4 ratings)
8.1
(8 ratings)
Likelihood to Renew
-
(0 ratings)
5.0
(1 ratings)
Usability
-
(0 ratings)
8.5
(3 ratings)
Performance
-
(0 ratings)
8.7
(3 ratings)
Support Rating
-
(0 ratings)
5.2
(2 ratings)
Ease of integration
-
(0 ratings)
8.5
(3 ratings)
User Testimonials
Azure API ManagementRed Hat JBoss Enterprise Application Platform
Likelihood to Recommend
Microsoft
APIM is useful for the standard scenarios:
1) Securing your back-end APIs - If you have a legacy back-end web service that has a basic authentication scheme, you can add some additional security by placing APIM in front, and requiring subscription keys. Leverage your existing firewall to ensure only your APIM instance can communicate with your back-end API, and you've basically added a layer of protection.
2) Lift and shift - there are always going to be clients that don't want to update their clients to use a newer API; in some cases you can make a newer API look like an older one by implementing some complex policies in APIM. You can also do the opposite, making older APIs look new, such as making an XML back-end accept both JSON and XML.
3) Centralizing your APIs - if you've acquired another company and want to make their API set look as if it's a part of the larger whole, APIM is an easy way to provide a consistent front-end interface for developers.
Read full review
Red Hat
JBoss EAP is subscription based/open source platform. It's very reliable and great for deploying high transaction Java based enterprise applications. It integrates well with third party components like mod_cluster and supports popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.
Read full review
Pros
Microsoft
  • Easy commissioning of APIs.
  • Great policies to control access.
  • Easy mock services for testing.
Read full review
Red Hat
  • MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments.
  • Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc.
  • Supports deployment in on-premise, virtual and hybrid cloud environments.
Read full review
Cons
Microsoft
  • Lack of robustness is a bit of an issue. Several other providers offer more options and capabilities, but then, they are lacking in interface ease.
  • As with anything Azure, pricing is really hard to stay on top of. I always find that you really don’t know what you’re paying for until you get the bill. Having an excellent Azure Administrator can help resolve that.
  • Integrating with app services outside of Azure can be a challenge, or at least much more challenging than just using Azure App Services.
Read full review
Red Hat
  • Jboss CLI is a great tool but we had trouble using it to get values that are displayed on Jboss GUI. It also has limitations parsing the applications.xml files and we had to use a mix of jboss-cli and linux bash commands to automate certain application administrative tasks.
  • JBoss doesn't really provides performance tuning recommendations. It would have been nice if it could learn from the current demand vs current settings for things like connection pool, server configurations, garbage collection etc.
Read full review
Likelihood to Renew
Microsoft
No answers on this topic
Red Hat
We are planning to migrate away from Jboss to Tomcat as Jboss has shown not interest in supporting OSGi which is heavily used at our shop
Read full review
Usability
Microsoft
No answers on this topic
Red Hat
JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.
Read full review
Performance
Microsoft
No answers on this topic
Red Hat
Usually, Red Hat JBoss Enterprise Application Platform is good at performance and well suited for high traffic Java EE-based applications, but we have faced hard times performance tuning it for our specific needs. The product would be nicer if they would add a performance diagnostic and recommendations feature to it.
Read full review
Support Rating
Microsoft
No answers on this topic
Red Hat
Fast response.
Read full review
Alternatives Considered
Microsoft
Azure APIM vs Amazon API Gateway:
1) Azure APIM was a complete package that included a developer portal.
2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.
3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway.
Read full review
Red Hat
We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.
Read full review
Return on Investment
Microsoft
  • We can always think of positive ROI impact on business
  • It helps to easily facilitate the design, deployment, and maintenance of our APIs
Read full review
Red Hat
  • Improved delivery timelines due to easy out of the box setup.
  • It is a cheap subscription-based/open-source Java EE-based application server. This reduces the overall cost of delivery.
Read full review
ScreenShots