This guide explores the architectural trade-offs, performance limitations, and modern design patterns (such as VRF-lite) to help you choose the right routing boundary for your enterprise. Routing on a core switch prioritizes raw forwarding performance. For enterprise network architects and senior infrastructure engineers, determining where Layer 3 routing logic should reside—on the core switch or the Next-Generation Firewall (NGFW)—is a foundational design decision. A misstep here can either cripple network performance with unnecessary. Routing is responsible for matching incoming HTTP requests and dispatching those requests to the app's executable endpoints. Endpoints are the app's units of executable request-handling code. Even the smallest FortiGate can forward a ridiculous amount of traffic as long as you aren't enabling IPS/SSL Decrypt/Antimalware. which you almost certainly don't. We're currently using a pair of Fortigate 600E's in Active-Passive HA, presenting 1Gb interfaces for our LAN, Management, STZ, DMZ which sit on separate switches. Route templates: Are defined at startup in Program. Are used to generate URLs for links.
[PDF Version]