Amazon's Elastic Load Balancing automatically distributes incoming application traffic across multiple targets, such as Amazon EC2 instances, containers, IP addresses, and Lambda functions. It can handle the varying load of your application traffic in a single Availability Zone or across multiple Availability Zones. Elastic Load Balancing offers three types of load balancers with the vendor states all feature the high availability, automatic scaling, and robust security necessary to make…
$0.01
Partial Hour
Cloudflare
Score 8.8 out of 10
N/A
Cloudflare, from the company of the same name in San Francisco, provides DDoS and bot mitigation security for business domains, as well as a content delivery network (CDN) and web application firewall (WAF).
We have not used any other solution out there in the market but our dev-ops team did deep research and AWS provided us the solution we needed to be cost-effective. Also, the decision to keep working with Amazon was strategic. We were already using other AWS features and [Amazon …
Cloudflare is the best option for my business for my use cases aligns exactly with what Cloudflare provides. Fastly only offers 1 month of free trial while AWS Route 53 is heavily integrated with AWS cloud. I want the flexibility to launch my own VPS and have a CDN, DDoS …
Cloudflare is notably simpler and cheaper as compared to CloudFront. If we also consider the corresponding edge compute mechanism, CloudFront has more complexity in maintaining it. For instance, in order to maintain our A/B test stack on CloudFront, we need to maintain three …
We use Amazon Elastic Load Balancers to serve mobile applications and websites. It works really well. We have not had any problems until now. Last year we integrated the AWS ELB with the EC2 Auto Scaling and now we have a fully working elastic solution. We increase/decrease EC2s instances based on traffic over our load balancers.
It is easy to set up, and within 10 minutes it is up and running. You can add many domains in one dashboard. So no need for a separate Cloudflare account. I can access all my domain DNS, and customize/add it further. For example by adding the Google Webmaster DNS key or my email provider.
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
Occasionally we have a huge number of users using our network at once, and Amazon ELB isn't quite fast enough to scale effectively when that occurs. But this doesn't happen very often as our usage is usually quite stable
If we want to add another application to our learning suite, we would have to add another load balancer, which would incur additional cost
The setup was not easy and could really only be handled by one person on our team with the technical background to do so
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.
AWS Elastic Load Balancing has this trick. First, you need to know how it works. ELB is not the only piece here. ELB has a very close relation with AWS Target Groups. You create or select a target group every time you create a Load balancer. Target groups allow you to connect the load balancer to EC2 autoscaling groups, Lambda functions, or even a single EC2 instance. While this sounds complex, it becomes easy, once you know his tricks. Thanks to the user interface, managing a ELB is an easy task. The rules editor is really useful, although it will need a bit of improvement to some interface items
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.
AWS gives you several support plans. On the free plan, you basicaly need to google for help, but the good news is that AWS Elastic Load Balancing works. We has more than 15 load balancers and we never run into a problem that require support. But you mght consider a support plan if you are going to do something more complex or critical
We really like to talk to a person on the phone or using chat. But the system is very slow and sending to much email to get the issue solve. Something we don't like to spend time writing on the community forum our issue because we don't want to share detail information of our POC.
We have not used any other solution out there in the market but our dev-ops team did deep research and AWS provided us the solution we needed to be cost-effective. Also, the decision to keep working with Amazon was strategic. We were already using other AWS features and [Amazon Elastic Load Balancing] integrates great with those.
Firebase can be a good starter for basic projects but as I scaled up, I found it lacking the maturity Cloudflare has. Naturaly, I opted for Cloudflare for bigger projects. I still use Firebase, but for small scale hobby projects only.
A lot of requests are cached and so egress costs from downstream providers are mitigated.
DDoS protection has also managed to keep our site up and our cloud computing bill down.
Setting up a proxy with a worker made putting various Google Cloud Functions running behind a single URL very easy and performant. Plus they offer API Shield on top of this.
