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
Heroku Platform
Score 7.6 out of 10
N/A
The Heroku Platform, now from Salesforce, is a platform-as-a-service based on
a managed container system, with integrated data services and ecosystem for deploying modern apps. It takes an app-centric
approach for software delivery, integrated with developer tools and
workflows. It’s three main tool are: Heroku Developer Experience (DX), Heroku
Operational Experience (OpEx), and Heroku Runtime.
Heroku Developer Experience (DX)
Developers deploy directly from tools like…
I use Bunny concurrently with Cloudflare. Both services are unique to each other while offering similar services. What Cloudflare has over Bunny is their numerous PoPs spread all over the world. Bunny still doesn't have a configurable WAF offering for the general public as of …
Cloudflare is less expensive with better performance. What more coudl you ask for?
Digitalocean has been great but when comparing costs to features, Cloudflare is cheaper for object storage and better performing across their large network.
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 …
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 is definitely a leader in the CDN space and is fending off well in the security area for web applications even when faced against vendors like Akamai which are more widespread and better known If Cloudflare keeps competitive prices and updated technology stack i …
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 …
Heroku was more extensive in terms of its operating and scaling from what we witnessed by looking into other options and trying to find the best operating system for a new platform.
Heroku Platform is cheaper to begin with compared to DigitalOcean or Amazon Fargate. The configuration user interface is also arguably easier to understand. With its user friendliness and cheaper tiers, Heroku Platform was our pick to host some of our applications that were …
I believe Azure App Service is pretty similar to Heroku as you can in both deploy your backend applications. However, the dyno concept and it's drastically simple web dashboard makes Heroku a much better and sane alternative to Azure app service. In Heroku, you get abstracted of …
Kuberbetes is an easily scalable docker based option which should need minimal DevOps, however, it has a pretty high learning curve with many decisions that need to be addressed as well as monitoring, logging and security concerns.
Heroku has the advantage of simplifying the development and integration with some services (which in Heroku they call addon) wherein other platforms, certainly for those who don't have much experience, it will take much more development time.
Heroku, in my opinion, is the easiest platform to deploy and host web applications on. From collaboration to deployment, everything is well thought out and bulletproof. If you need advanced server functionality, like a VPC, machine-to-machine communication, etc., you will …
We also use Cloud 66 which provides some of Heroku's features, at a lower price. It still cannot compare to Heroku's ease of use and ability to easily deploy new staging environments though, so we will always use Heroku for at least some of our projects.
Heroku is an all in 1 package for deploying and running your services. It provides an easy to use setup and run for 90% of cases. If you have a more complicated infrastructure, you'd definitely need to move to another hosting provider. But if as long as you can operate within …
Heroku has advantages over Docker, Google App Engine and AWS products, but it depends largely on your use case. If you are already in AWS, it's probably in your best interest to stay with AWS products. However, other "Cloud Formation/Orchestration" products like Docker are …
We kicked the tires on OpenShift before deciding on Heroku, and found the platform to be much less intuitive and well-documented than Heroku. It felt like we were constantly trying to implement workarounds for esoteric platform problems, and eventually the work became too …
For a different project, Aptible surpassed Heroku when it came to meeting HIPAA-related requirements, though it offers much less flexibility with add-on services (for obvious reasons). Google App Engine had a much more complicated deployment model and seemed unnecessarily …
To this day no other PaaS matches Heroku in ease of use and maturity. If you want to stay 100% focused on your unique product/service rather than wasting time on boilerplate hosting issues, I can highly recommend Heroku. I personally use it for all of my own websites …
Heroku is the more expensive option for hosting compared to some of the cloud platforms we investigated, but it's worth it for us because of the plug-and-play nature of Heroku deployment. We can be up and running in a few minutes and know with precision how much it will cost us …
Heroku has the easy facility to deploy and host applications while others have to configure a lot. The price of the services is high for others. But within Heroku pricing and easy to maintain under the same roof.
Some APIs are specifically developed to be deployed to certain platforms and usually decision which platform to use is not developer's. Another question is deployment cost and pricing model; in specific cases after price comparison Heroku is often selected among other cloud …
Heroku is a really great platform to get up and running QUICKLY and efficiently. What Heroku is really great at that other services are lacking is ease of use, documentation. It is really great for beginning developers and awesome to get up and running to take care of lots of …
I feel Heroku is lightyears ahead of all other PaaS offerings. To me the competition is between PaaS and self-hosted cloud, not between Heroku and other PaaS providers.
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.
Heroku is very well-suited to early stage and/or rapidly changing projects. It is great for getting moving quickly or changing direction quickly. In scenarios where there is already scale or well-defined requirements, it may be preferable to set things up directly on AWS or another cloud provider to avoid the additional costs of Heroku as the middleman.
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
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.
Could be less expensive, although you get what you pay for
Sleeping apps can be an annoyance: Heroku automatically puts your apps in sleep mode and they have to spin back up after periods of inactivity. Much of this can be solved but it requires working around the built-in functionality. I understand why they do it but it's an area that could be improved.
Restrictions to server access means you can't customize as much as you could if you owned the server. But again, this is also a benefit because it's about convention over configuration. So you can't configure as much, but then, you typically don't have to.
Heroku is a critical and core part of our infrastructure that is serving our customers well. We are very satisfied with the cost of our solution. While it would be difficult to move away from Heroku, we have no plans to do so. We have had no major issues with it and it is a pleasure to use. Other products on the market might offer comparable functionality, but until we expose a need that Heroku cannot satisfy, we'll stay the course.
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.
Deploying apps, scaling , managing environment is very simple. Clean interface for logs, metrics and app settings. Deployment is fast. Don't need deep knowledege of devops or cloud. Buildpacks, pipelines, and review apps makes work easier. Detailed guides help solve common problems fast.
Pricing is higher at scale. Autoscaling options are limited.
Heroku availability correlates pretty strongly to AWS US EAST availability. We had a couple of times where there was a Heroku-specific issue but not for the last 7-8 months.
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.
I've used it for many years without facing any major problem. It's not hard at all to get used to it, it's documentation is outstanding and simple. We are close to 2020 and I don't think most of the existing companies or startups should still face old problems such as wasting time deploying code and calculate computing resources.
Be ready to pay a bit more than expected in the beginning if you're migrating from a big server. The application is probably not ready for the change and you have to keep improving it with time.
It's also important to consider that you can't save anything to the disc as it will be lost when your application restarts, so you have to think about using something like S3.
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.
Heroku has advantages over Docker, Google App Engine and AWS products, but it depends largely on your use case. If you are already in AWS, it's probably in your best interest to stay with AWS products. However, other "Cloud Formation/Orchestration" products like Docker are typically lacking the ease-of-use factor that allows you to get up and running with Heroku quickly.
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.