# Network Design Lesson: Split Functionality Across Devices When Appropriate

DevFeed: [Network Design Lesson: Split Functionality Across Devices When Appropriate](<https://devfeed.tech/articles/must-read-make-two-trips-11016.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2024/05/worth-reading-make-two-trips/>)

Published: 2024-05-29T06:33:00Z

Content type: opinion

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Network design](<https://devfeed.tech/topics/network-design.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>)

Tags: [bugs](<https://devfeed.tech/tags/bugs.md>), [network](<https://devfeed.tech/tags/network.md>), [network-design](<https://devfeed.tech/tags/network-design.md>), [worth-reading](<https://devfeed.tech/tags/worth-reading.md>)

## AI overview

The article argues that network designs can be simpler and less costly when required functionality is divided across multiple devices instead of being crammed into one device.

## Source excerpt

Tom Limoncelli wrote another must-read masterpiece: sometimes you'll save time if you make two trips instead of one. The same lesson applies to network design: cramming too many features into a single device will inevitably result in complex, hard-to-understand configurations and weird bugs. Sometimes, it's cheaper to split the required functionality across multiple devices.