Insights from the load balancer experts

Talking about the cloud and actually moving to the cloud are two very different things.

If you want safe, easy-to-use object storage software then the Hitachi Content Platform (HCP) is it. But why, and how, can you optimize this solution with load balancing?

We'd all rather prevent a disaster than have to live with the consequences of one.

We're going to have a look at setting up a Layer 7 VIP, which will connect back to our MinIO servers.

The use case for object storage in hospitals, and why it needs a dedicated load balancing solution.

Growing customer demands are forcing technology providers to reconsider their approach to high availability and scalability.

Before we can connect to the loadbalancer appliance using SSH, we first need to allow this action through the Appliance Security Options via Local Configuration and then, Security.

As with the majority of Loadbalancer.org's projects in the Middle East, the goal of this project was to help a group of hospitals achieve highly available medical imaging systems.

Why do you need TWO load balancers?

Sometimes, we need to pass unusually large HTTP requests through our WAF stack.

The focus will very much be on re-living all that's happened to the royal family in those 70 years. But that means digging deep into the media archives...

A while ago I was asked if it would be possible to apply some general rate limiting in HAProxy and the WAF, in order to help prevent DOS-style attacks on a customer's servers.

F5 recently announced a critical security vulnerability, allowing an attacker to bypass its iControl REST authentication, and execute commands such as creating or deleting files and disabling services.

On May 11th 2022, I was listening to the awesome Chris Moyles Show, on Radio when a site they were using crashed while they were on air.

Email notifications are a great way of alerting you to any changes or issues within your load balancer or high availability cluster.

It's a fair question, right? Let's take away the strain of SSL terminations from our application servers and let the load balancers deal with it. After all, why would we want to bog down our nifty application with network-level considerations?

Load balancing? Say what?! Got 2 mins to get your head around the concept? Your time starts....now!

It is understandable that SysAdmins, DevOps, and most in the IT and Security Departments involved want to ensure all load balancers are fully patched and protected, given that our product plays an important role in their topology.

The only real reason for separate network ports is physical redundancy. Because the other primary reason (security segregation) can be easily implemented using VLANs.

At Loadbalancer.org, our heroes are open source. And for good reason. Open source software plays an intrinsic part in our company, products, and services.

Customers with manually configured, custom client authentication deployments (rare) or using “re-encrypt to backend” to communicate with untrusted third-party servers (very rare) may be impacted.

As you know, we get excited about solutions, not semantics, so I'm going to go against the grain here and say 'Application Acceleration' is one of those buzzwords that's about as useful as all that designer water that's out there these days.

Many things in tech are over-complicated for no reason, and iRules are a prime example of that.

The topic of hardware replacement, trade-in, and upgrade options is rife with opinions, bad habits, and rules of thumb. It gets even more complicated when you consider how your choices are affected by your vendor's randomly changing end-of-life policies.

For the uninitiated, layer 4 DR mode is a high performance load balancing method available on our appliances. It works by having all response traffic flow from the servers straight back to the clients.