I am excited and looking forward to be a speaker at the DevOps Pro Europe 2019 in Vilnius. My first time in Lithuania, talking about “MySQL on the Cloud: a Journey from Virtual Machines to Serverless Deployments”. You can read the abstract of the talk here.
How can software developers and startups manage location-based services in disputed territories or partially recognized state? Looking forward to present “Hey, where is my country? Software development and territorial disputes” at Factory Berlin.
This event is for members only but if you are interested get in touch, I will discuss location-based services in disputed territories or partially recognized state at other events in Berlin and Cologne in the next few weeks.
Cross Zone Load Balancing is one of the less known and most confusing options of the different load balancers on AWS. Until 2013 the choice was simple, Amazon offered only one load balancer as a service – the Classic Load Balancer – and there was no option to perform Cross Zone Load Balancing. No feature, no doubts, no extra costs.
In 2019, with three different load balancers (Classic Load Balancer, Application Load Balancer and Network Load Balancer), there is much more flexibility but as well a higher risk of an incorrect configuration or unexpected charges.
What is Cross Zone Load Balancing?
As for AWS documentation:
“With cross-zone load balancing, (…) each load balancer node distributes requests evenly across the registered instances in all enabled Availability Zones. If cross-zone load balancing is disabled, each load balancer node distributes requests evenly across the registered instances in its Availability Zone only.”
What is the default for the Cross Zone Load Balancing?
Unfortunately the default is different on every load balancer and not very intuitive. As for AWS documentation:
Classic Load Balancer: with the API or CLI, cross-zone load balancing is disabled by default. With the AWS Management Console, the option to enable cross-zone load balancing is selected by default.
Application Load Balancer: cross-zone load balancing is always enabled
Network Load Balancer: cross-zone load balancing is disabled by default. You can enable or disable cross-zone load balancing at any time.
Should I always enable it?
There are many documents and posts on the benefits of enabling cross-zone load balancing. And if you have only one target in every Availability Zone, it is usually an easy choice . But what are the main reasons to disable it or keep it disabled?
Maybe you want to minimise the latency between your load balancer and the application nodes and have all the traffic in the subnet. Or you take advantage of the SSL termination on the load balancer and you do not want to manage not encrypted traffic across data centres and different subnets. Or maybe you want simply to save a few dollars.
Do I pay extra for Cross Zone Load Balancing?
You do not pay for the the feature itself but you might pay for the generated regional data transfer. The voice that in your billing ends up under
$0.010 per GB - regional data transfer - in/out/between EC2 AZs or using elastic IPs or ELB
and that can end in significant charges if you manage large binaries on your load balancers. According to the AWS FAQ, the cost varies according to the specific service.
Q: Am I charged for regional AWS data-transfer for cross-zone load balancing in Application Load Balancer?
A: No. Since cross-zone load balancing is always on with Application Load Balancer, you are not charged for this type of regional data transfer.
Q: Am I charged for regional AWS data-transfer when I enable cross-zone load balancing in Network Load Balancer?
A: Yes, you will be charged for regional data transfer between Availability Zones with Network Load Balancer when cross-zone load balancing is enabled
Q: Am I charged for regional AWS data-transfer when I enable cross-zone load balancing in Classic Load Balancer?
A: No, you are not charged for regional data transfer between Availability Zones when you enable cross-zone load balancing for your Classic Load Balancer.
Cross Zone Load Balancing is a very useful feature and you likely end up enabling it in many common scenarios. But it is vital to understand the default values and the implications according to the specific AWS service you choose.
I passed my first AWS Certified Solutions Architect exam in 2013 when there was only one option available. As recertification is (was) required every 2 years, I did take the (Professional) Architect exam in 2015, 2017 and (happily) again today. Now I can wait 3 more years, for a total of 9 years since my very first one. And I hope that by 2022 the questions with RRS or SWF will be finally gone.
I am happy to share the video of my presentation MySQL on the cloud, from virtual machines to serverless options at the latest DevOpsConf in Moscow. Very glad I had the chance to talk about databases on the cloud, attend an interesting conference in Russia and meet many software engineers. The slides of the talk are available too.
Talking pasta & AWS in Poland: how many penne and spaghetti can you (manually) set up before your cloud deployment is not manageble anymore? The video of my presentation at the SFI in Krakow
Going off the beaten track and the most popular conferences in Western Europe lets you have a different prospective, meet very skilled DevOps and challenge your technical knowledge. Very glad to talk about “MySQL on the cloud, from virtual machines to serverless options” at the DevOpsConf Russia in Moscow.