Initially, the load balancing (balancers) feature was a significant milestone in infrastructure development. Although in some well-known panels it has been prone to issues like latency, disconnections, exposure to intrusions, and more, it remains a crucial part of these systems' architecture.
After extensive analysis over time, I’ve pinpointed critical improvements needed in this layer, and I am committed to developing it with a focus on solving these persistent problems.
One key feature that will be part of the breakthroughs in this project is the integration of a custom CDN solution. Many are quick to use any available CDN they find online, which often carries risks such as IP exposure or even server blacklisting.
My plan is to add this critical layer, not just for the obvious benefits:
- Caching for optimized performance.
- High availability across geographical zones.
- Mitigating server attacks (DDoS).
- And more.
But more importantly, I am focused on protecting the servers' IPs. It’s widely known that many governments enforce service blocks by blacklisting IPs, and this layer will address precisely that by allowing you to:
- Rotate IPs regularly.
- Never expose the real server IP.
- Easily replace this layer (small nodes) instead of your entire infrastructure, saving you both costs and time.
In my research and development toolbox, I also have P2P streaming modules that I worked on in the past, but that’s something I’ll unveil further down the road.
For now, I leave these thoughts here, open to interpretation and debate.