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
F5 Distributed Cloud DNS
Score 8.2 out of 10
N/A
More than 75% of enterprises today operate in multiple clouds, according to the 2022 F5 State of Application Strategy Report. But a much smaller percentage are known to have implemented a cloud-based DNS (Domain Name System), which offers considerable speed and performance benefits for publishing applications. Why? It is because extending traditional DNS to all their applications across different environments, especially those running in the cloud, can be time-consuming and…
N/A
Pricing
Amazon Elastic Load Balancing
F5 Distributed Cloud DNS
Editions & Modules
Gateway
$0.0125
Partial Hour
Application
$0.0225
Partial Hour
Network
$0.025
Partial Hour
No answers on this topic
Offerings
Pricing Offerings
Elastic Load Balancing
F5 Distributed Cloud DNS
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Elastic Load Balancing
F5 Distributed Cloud DNS
Considered Both Products
Elastic Load Balancing
Verified User
Anonymous
Chose Elastic Load Balancing
Again as noted we're still in the trial process seeing if we want to migrate over but the biggest benefit of elb is its interconnectivity with other Amazon web services hosted applications that our company is using and the in-house support from AWS. This is very attractive when …
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 …
In the past we use physical Load Balancers. That solution works, but it had several negative points. The first, it was not elastic. It requires a physical server setup in order to work. Also a technician works for one or more days to set up the solution. And then, we had the …
It really is a straight-up situation. From my current experience if you have two or more services hosted on Amazon web services that need transactions between each other with a variable flow of traffic then elb is a fantastic method for routing that traffic and making sure that no one back and component gets overloaded with requests while other existing components are just standing there idle waiting for some traffic. As noted earlier in my review we are still doing a trial run with the service as not all of our components are hosted on AWS yet and we aren't having as great luck with transactions between hosted and non-hosted but that could also simply be a learning curve on our part.
Probably less appropriate for smaller, very small IT departments, but more suited like when you're doing migrations to the cloud. If it is going to be doing setups for DNS within the cloud, this will let you help you set it up so there's no loss of communication between the two.
I think probably the UI, it's very easily you could scan through and select what you're going to do, and it's kind of similar of the functionality when you compare it to say the Oracle Cloud. So you can go side by side with the windows and then just go through these level when you're going to sell like a new DNS or a new opening on that.
Probably more like AI suggested customizations, like when you do something and then have something like in the background of the AI. When you start doing something, it'll show you what you previously have done and then you could select, you wouldn't have to go through the whole steps over again. It'll say this is what you've done before, do you want to do a copy? And then just modify a couple of things so you don't have to go through the whole process.
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
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 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.
I guess positive because we know when we're going to open up, say a DNS or anything, or we're going to have to set something up. We can do it quick and fast instead of having to wait longer for the different steps of how we used to do it before.