An engineering historian converted network infrastructure to Roman aqueduct principles. Two-thousand-year-old water systems apparently have better uptime than microservices. The developer marched off to build actual aqueducts after realizing stone arches are more reliable than cloud architecture. Your task: Route data packets through Roman-inspired network aqueducts with gravitational flow optimization.
Why You're Doing This
You're building a network routing system based on gravity-fed water distribution with elevation constraints. This tests network topology optimization, resource flow management, and routing with physical constraints. It's like BGP but with more marble and fewer packet drops due to superior Roman engineering.
Take the W
✓ Routes data using gravitational flow principles
✓ Optimizes paths based on elevation differences
✓ Maintains network connectivity with Roman engineering constraints
Hard L
✗ Ignores elevation data in routing decisions
✗ Allows data to flow uphill without pumping stations
✗ Produces routes that violate Roman engineering principles
Edge Cases
⚠ All network nodes at identical elevation requiring pumping station infrastructure
⚠ Data routing to destinations higher than any available source nodes
⚠ Network capacity limitations during high data volume periods like gladiator games
Input Format:
Network nodes with elevation data, data payload size, destination requirements
Expected Output:
Optimal aqueduct route with flow time and maintenance requirements