Hi! thanks for the idea! really cool. But just one question, why I would need to create a load balancer of my app if I will use kubernetes or other orchestrator that has already its own load balancer? Thank you so much!
Most likely you will not need to create a custom load balancer for your app since majority of popular load balancers already cover numerous use cases. Even if there is something complex going on there will be achievable solution using existing tools which may require some workarounds but most likely will be better than writing something from scratch. Moreover, you will not use this in production of course, because there are more advanced and battle tested approaches. However, it's a good exercise to practice the skills. Developers build different projects for learning purposes, for understanding ideas and because it's fun! Same goes for building the unix word count, cut, json parser, Redis clone, chat server or any other project. These things already exist out there and they are more advanced, but the goal is to get the gist of it and understand how something works.
Load Balancers are network-based appliances. The transition from software-based load balancing to hardware-based solutions occurred during the earlier stages of the software era. Today, load balancers have evolved into scalable virtual Application Delivery Controllers (ADCs) that can be instantiated in the cloud using Infrastructure as Code (IaC) in DevOps environments.
Yes, the EmberServerBuilder in http4s is built on top of the BlazeServer, which is an HTTP server implementation provided by the http4s library. Blaze is an asynchronous, non-blocking, and high-performance HTTP server designed to handle a large number of concurrent connections efficiently.
Great video!
Watching coding is always a great inspiration
Thanks for being one of the best sources of information in the Scala world :D also, nice video mate!
So simply said Dan, loved it.
I like all the scala videos, thanks
Hi! thanks for the idea! really cool. But just one question, why I would need to create a load balancer of my app if I will use kubernetes or other orchestrator that has already its own load balancer? Thank you so much!
Most likely you will not need to create a custom load balancer for your app since majority of popular load balancers already cover numerous use cases. Even if there is something complex going on there will be achievable solution using existing tools which may require some workarounds but most likely will be better than writing something from scratch.
Moreover, you will not use this in production of course, because there are more advanced and battle tested approaches. However, it's a good exercise to practice the skills. Developers build different projects for learning purposes, for understanding ideas and because it's fun! Same goes for building the unix word count, cut, json parser, Redis clone, chat server or any other project. These things already exist out there and they are more advanced, but the goal is to get the gist of it and understand how something works.
@@scalevolvable323understood! thanks ❤😊
Load Balancers are network-based appliances. The transition from software-based load balancing to hardware-based solutions occurred during the earlier stages of the software era. Today, load balancers have evolved into scalable virtual Application Delivery Controllers (ADCs) that can be instantiated in the cloud using Infrastructure as Code (IaC) in DevOps environments.
Thank you....
is your load balancer multithreaded?
Yes, the EmberServerBuilder in http4s is built on top of the BlazeServer, which is an HTTP server implementation provided by the http4s library. Blaze is an asynchronous, non-blocking, and high-performance HTTP server designed to handle a large number of concurrent connections efficiently.