Hardware vs. Software Redundancy


We have always taken redundancy very seriously at Incognito, and for years, we have ensured that our products have been clusterable and redundant. You can read more about our DHCP redundancy here. It definitely adds a large degree of complexity, but is well worth it in the end.

Over the last few years however, hardware redundancy has surfaced as a real contender in improving system resiliency. What would I put my money on? Software redundancy. This is because with hardware redundancy, the software is not aware that it is being monitored, which may affect the final results. Personally, I don’t like to use an application that relies entirely on a third party’s perception of how the application should operate, and so I feel more secure using well-designed software redundancy.

The other problem with activating a hardware redundancy solution is that it may take longer to implement than its software counterpart. On the flipside, designing a proper software redundancy system is such a difficult process that in some cases a hardware solution may be your only option. At Incognito, we support both systems in our solutions, as well as support virtualization, which in some cases could be considered a form of redundancy. We have customers using all three methods successfully, so you can feel confident knowing that you have the choice to use whichever approach best suits your network. Regardless of your decision, rest assured that we can support you just the same.

  • Share: