Microsoft's Azure API Management supports creation of API.
$0.04
Lightweight and serverless version of API Management service, billed per execution
Cloudflare
Score 8.7 out of 10
N/A
Cloudflare’s connectivity cloud is a unified platform of cloud-native services designed to help enterprises regain control over their IT environments. Powered by an intelligent, programmable global cloud network, it is built to offer security, performance, visibility, and reliability.
$20
per month
Pricing
Azure API Management
Cloudflare
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
Apigee is by Google and seems to be promising. The cost seems high though. With Azure, we do not have to make any special purchases. CapEx vs OpEx! But, Apigee could be more environment independent compared to Azure APIM. The promise of speed by Apigee is also better compared …
It’s a great tool, and so easy to seamlessly connect into your current Azure world that it’s hard not to look at it or even test the waters with it. It’s priced well, and is feature-rich enough to accomplish most tasks. I think the ease of having everything together and the …
A few years ago, GoDaddy started charging us to be their DNS provider, and Cloudflare didn't charge, so we moved to Cloudflare. Also, Cloudflare was known for security protection, for example DDOS protection, and we haven't had any issues since moving to Cloudflare.
Cloudflare is on another level compared to any other CDN provider out there. One of the reasons is that encompasses all the tools into one big products instead of relying on many different products from many companies - DNS, CDN, WAF are all managed in one place and connected …
Cloudflare was better, because we do not have to host or purchase any additional hardware. This means reduced costs for us to have to buy the hardware. Then, hire people to run the hardwar, and support the hardware. And, it also means you need SME's for the tool that have used …
Cloudflare's product offering is more mature and has demonstrated success in preventing some of the largest DDoS attacks observed. Cloudflare also continues to reinvest in their core product offering to ensure they maintain a position as leader in the cybersecurity space.
Cloudflare knows what they're doing when Load Balancing and Redundancy meet the cloud. AWS is a partner, and we're exploring other solutions which are performing at the highest level.
Peak season is upon us, and we cannot suffer downtime. DDoS Protection is another interesting …
Amazon CloudFront is a highly scalable CDN service integrated with AWS. Couldflare provides us more other functions and services than Amazon CloudFront. Google Cloud CDN offers fast and reliable content delivery with integration into Google Cloud services. But we didn't deploy …
Cloudflare addresses Pipefy a well-defined cache system with several features to improve the performance of the applications. This is the main focus + excellent reliability and stability.
Overall we are using Cloudflare as well as AWS cloud across various domains in our organization. To some extent such as DNS management on Route53, CloudFront takes advantage of Cloudflare as it provides a straightforward UI for DNS management. But when it comes to traffic …
Better than other software in the same field as per price time to implement easy to learn and use, good simple easy to understand user interface and very few false positives plus our compliance with cyber insurance is right on the money we no longer have to jump extra hopes to …
ZScaler Private Access and Cloudflare Access are very similar product sets that trade blows when it comes to features and capabilities. In my experience Cloudflare unified dashboard and distributed infrastructure has the upper hand when compared to ZScaler.
Cloudflare has lower starting cost for backend Workers and good pricing model with steps. Auto-scaling by default better than microservice/docker or EC2. Security makes simpler.
The range of policies that enable the APIs to loosely couple it with security, rate limit, retry, etc. are good. We can easily tie authentication mechanisms to external and other internal services without having to modify the backend.
Cloudflare works well as security measure that gives peace of mind without needing to work too hard to get it functioning well. It provides great tools to customize the security experience as well. This is all the same for the caching tools as well. They have a lot of built in tools that make using the caching easy right out of the box, but they provide the customization options to get things just right for your site.
Registrar and DNS services are impeccable, with registrations done at cost and without ADs. DNS services setting standards for speed of resolution.
DDOS protection. With their content distribution network to back them they have the bandwidth and tools to be both proactive and reactive to bad actors.
WAF - Their Web Application Firewall helps mitigate common site vulnerabilities and has active zero-day protection running for breaking exploits
Cost - the upfront cost is a bit restrictive. I've been told it is because there are a few underlying VMs that are running this service. So if you're just starting out with API management, it can be an expensive proposition. Value increases as you add additional APIs. If you're using Azure B2C for the developer portal, you'll require Standard or Premium since they support AAD integration.
Security granularity - at time of writing, APIM doesn't support breaking out operations to products. For example, if you have an API that has a GET and a POST operation, and you want the POST operation to require a different subscription. There is a work around, but it makes management a bit messy.
Developer and Publisher portal - it's a little weird. Microsoft hasn't migrated all the publisher portal functionality into the "native" Azure portal. So some of it feels a little weird - especially when working with the content management side of things for the developer portal.
Scaling - while it's easy to scale up, the cost of APIM ramps up very quickly. Standard -> Premium is a 4x jump.
In some cases, using Cloudflare can actually lead to slower website speeds if the network is congested or if the website's traffic is particularly heavy.
Some website owners may find that the level of customization offered by Cloudflare is limited, especially in comparison to other solutions.
While Cloudflare is easy to set up and manage, it may be too complex for users who are not familiar with web technologies.
Everything is extremely concise and all settings apply immediately and take effect globally. There is no reason to explicitly plan/think in terms of individual regions as one would have to traditional cloud offerings (AWS, OCI, Azure). All Cloudflare products integrate seamless as part of a single pipeline that executes from request to response.
I have only used their support a few times, and most times, they are responsive and able to resolve my issue with a minimal amount of time and effort. However, there was one instance where I simply asked about how to purchase some more resources (redirect rules), and I received some type of automated/AI response that was very unhelpful and gave me no opportunity to escalate to a person.
Nothing like it. Organizations can utilize these Cloudflare products to enhance their online presence by improving security, performance, reliability, and developer efficiency. Cloudflare is an American company that delivers services such as DNS, a content delivery network (CDN), and various other additional services to make websites faster and more secure. Cloudflare is used by over 26 million sites, resulting in the processing of more than 1 billion IP addresses each day.
It’s really pay as you go, so it's not that costly to get in and try it out. There’s no expensive client to buy and manage, but you do need to stay on top of the rapidly changing Azure environment to be sure you upgrade or adjust when needed.
It’s not great having more than one API tool, but it’s ok to spread out your work, as you always want the right tool for the right job. For example, if you are a Salesforce-heavy organization, I’d go with Mule over Azure.
It was easy getting an external consultant access to the tool to build their own API for a project they were working on for us.
We have seen reduced usage and downtimes after using Cloudflare for Caching. This has already yielded ROI as minimal downtime ensures consistent user traffic and increases revenue.
It can handle significant traffic spikes and shields the website from DDOS attacks. We have prevented a number of DDOS attacks after using Cloudflare and hence we are already seeing an ROI by using it.
Some of the integrations with Cloudflare are really painful and we have faced a lot of issues because of not having native integrations to certain 3rd party apps.
