Senad Caus Senad Caus | Mai 29, 2022 | Load Balancing/Routing, Webinars
Mittwoch, 15. Juni 2022 US: 12 Uhr EDT, 11 Uhr CDT, 10 Uhr MDT, 9 Uhr PST EU: 18 Uhr MESZ, 19 Uhr MESZ Global: 16 Uhr UTC Die Version 2.6 des weltweit schnellsten und am weitesten verbreiteten Software Load Balancers wurde veröffentlicht! Darin enthalten sind wichtige...
Senad Caus Senad Caus | Apr 4, 2022 | Load Balancing/Routing, Webinars
HAProxy ALOHA is a load balancer that’s ideal for companies in search of high performance and ease of use. It comes as either a hardware appliance or a virtual appliance and provides load balancing of TCP, UDP and HTTP traffic, DDoS protection, and active-active...
Senad Caus Senad Caus | Feb 20, 2022 | DevOps, Webinars
The HAProxy Data Plane API enables you to configure your HAProxy load balancers programmatically. This latest release, version 2.5, expands coverage of existing HAProxy configuration directives, fixes bugs, and optimizes performance. During this on-demand webinar, you...
Senad Caus Senad Caus | Jan 26, 2022 | Basics, Load Balancing/Routing, Webinars
A common misconception is that load balancing is enough to achieve high availability. That is only true when you factor in one, very important feature: health checks! Health checks monitor your servers for issues. If a server loses connectivity or begins returning...
Senad Caus Senad Caus | Nov 21, 2021 | Load Balancing/Routing, Load Balancing/Routing, Webinars, Webinars
Datum und Uhrzeit des Webinars: Dienstag, 14. Dezember 2021 US: 12pm EST, 11am CST, 10am MST, 9am PST EU: 18 Uhr MEZ, 19 Uhr EET Global: 17 Uhr UTC HAProxy 2.5 ist jetzt verfügbar! In dieser Sitzung erfahren Sie mehr über die Änderungen. Diese Version von HAProxy...
Senad Caus Senad Caus | Aug 20, 2021 | Kubernetes, Load Balancing/Routing, Technik, Webinars
If you prefer to watch the French version of this webinar, register here. Traditionally, connecting clients to services in Kubernetes has required multiple layers of proxies. For example, an external load balancer will route traffic to your nodes. Then, kube-proxy...