Open Source C# Load Balancers

Npgsql is an open source ADO.NET Data Provider for PostgreSQL, it allows programs written in C#, Visual Basic, F# to access the PostgreSQL database server. It is implemented in 100% C# code, is free and is open source. An Entity Framework Core provider is also available and exposes some features unique to the PostgreSQL database to EF Core users. Finally, a legacy Entity Framework 6.x (non-Core) provider is also available but is no longer being actively maintained. Npgsql is the open source .NET data provider for PostgreSQL. It allows you to connect and interact with PostgreSQL server using .NET.

JPPF makes it easy to parallelize computationally intensive tasks and execute them on a Grid.

It is a versatile DNS Proxy server with DNS firewall which filters DNS traffic between local computer and DNS servers with flexible rules, supports blocking by IP geography, caching, import/export rules into XML. With a click of a button acts as a DNS proxy (or DNS server), supports multiple client authentication methods, calculates statistics for DNS servers and proxy clients, supports load balancing between multiple upstream DNS servers.

This client-server application allows a master computer to distribute tasks to other slave computers and later join the results. Goal is for the master computer to handle lost connections and load balancing.

DotNetMQ is a message broker (message queue, message oriented middleware) that has several features including guaranteed delivering, routing, load balancing, server graphs... so on. See article on CodeProject.com for more information: http://www.code

NLog is a logging platform for .NET with rich log routing and management capabilities. It uses familar logger pattern known from log4xxx. Advanced routing options include buffering, asynchronous logging, load balancing, failover, and more.

Network Manager is a free and open source Windows tool that will aid you in monitoring and configuring your network adapters.

Quartz.NET is a full-featured, open-source job scheduling system that can be used from smallest apps to large-scale enterprise systems. Can run embedded within an application or even instantiated as a cluster of stand-alone programs (with load-balance and fail-over capabilities). Jobs are scheduled to run when a given trigger occurs, triggers support wide variety of scheduling options. Jobs can be any .NET class that implements the simple IJob interface, leaving infinite possibilities for the work jobs can perform. Job stores can be implemented to provide various mechanisms for the storage of jobs, in-memory and multiple relational databases come supported out of the box. Built-in support for load balancing your work and graceful fail-over. Applications can catch scheduling events to monitor or control job/trigger behavior by implementing one or more listener interfaces.