3 ms·
Networking is a combination of hyper-specific hardware solutions "this ASIC targets the mid sized enterprise core and has features specialized to doing that rol
by zamadatix 3y ago
Networking is a combination of hyper-specific hardware solutions "this ASIC targets the mid sized enterprise core and has features specialized to doing that role best, the lower tier version from even the same manufacturer and family however has these limitations... and this carrier focused L2 switch seems similar at a glance but actually has a nearly non-overlapping choice of hardware features baked in" and few (outside of the hyperscaler-like crowd) who actually want to manage that themselves despite knowing no generalized solution is really ready to manage it well either. This results in a massive amount of NOS customization and backwards compatibility that changes horizontally, vertically, and each generation in time. In the meantime, anyone who thinks they can optimize a specific use case better can introduce a new weird device and become popular because it achieves that use case at a great price.
That said, things have been moving in the right direction. E.g. the newer "Nokia Router OS" SR Linux is "just" bog standard Linux with a microservices based service layer which implements industry standard APIs for configuration and telemetry streaming. It still has a lot of legacy stuff, and even a replica of the classic CLI built on top of these APIs, but there is a bit more convergence in that I've been able to deploy Nokia gear and Arista gear in the same DC and manage them as one EVPN fabric with mostly identical API management to get there.
The short version of the above is there are still so many disparate weirdo systems precisely because the use cases of networking are well fit for wildly differentiated hardware every iteration which then drives having specialized software to go with it. Until that advantage goes away I don't see the networking space consolidating all that much.