MVC Routing - Using NGINX to route instead of PHP (or Ruby, etc.)
I'm currently messing around with making a custom MVC framework for educational (and, if it's good, actual practical) use, and I like to investigate different scenarios for possible performance boosts.

When it comes to URI routing, I'm familiar with the standard URI format of

    /controller/action/id

And parsing the data out of this to control the routing wouldn't be too difficult. Now, what I'm moreso wondering about is the performance difference between having nginx parse this URI string out into a query string of some type to pass to a controller directly, so that would end up like

    /foo/bar/12 => /application/foo.php?action=bar&id=12

instead of

    /foo/bar/12 => /index.php?controller=foo&action=bar&id=12

or even

    /foo/bar/12 => /index.php?uri=/foo/bar/12   (note that this would be encoded)

I'm aware that nginx passes the url, query string, and other things to php-fpm in other variables already, but this is just for illustrative purposes to show what I'm thinking.

Is this a stupid thing to do? I know that by defining routes explicitly in nginx would mean me needing to restart nginx every time I alter the routes in the config, which could be a downside.

So, to restate the question: When it comes to MVC routing, is there any worthwhile performance gain by having the actual webserver (in this case, nginx) itself handle the routing to the controller OR is using a standard landing script (like index.php in the root of the directory) and passing along the URI to be parsed for routing perfectly fine?

Thanks ahead of time. Also, I'm just learning about these things, so I wholeheartedly welcome suggestions on what I should be doing instead.
MVC Routing - Using NGINX to route instead of PHP (or Ruby, etc.)
===

I'm currently messing around with making a custom MVC framework for educational (and, if it's good, actual practical) use, and I like to investigate different scenarios for possible performance boosts.

When it comes to URI routing, I'm familiar with the standard URI format of

    /controller/action/id

And parsing the data out of this to control the routing wouldn't be too difficult. Now, what I'm moreso wondering about is the performance difference between having nginx parse this URI string out into a query string of some type to pass to a controller directly, so that would end up like

    /foo/bar/12 => /application/foo.php?action=bar&id=12

instead of

    /foo/bar/12 => /index.php?controller=foo&action=bar&id=12

or even

    /foo/bar/12 => /index.php?uri=/foo/bar/12   (note that this would be encoded)

I'm aware that nginx passes the url, query string, and other things to php-fpm in other variables already, but this is just for illustrative purposes to show what I'm thinking.

Is this a stupid thing to do? I know that by defining routes explicitly in nginx would mean me needing to restart nginx every time I alter the routes in the config, which could be a downside.

So, to restate the question: When it comes to MVC routing, is there any worthwhile performance gain by having the actual webserver (in this case, nginx) itself handle the routing to the controller OR is using a standard landing script (like index.php in the root of the directory) and passing along the URI to be parsed for routing perfectly fine?

Thanks ahead of time. Also, I'm just learning about these things, so I wholeheartedly welcome suggestions on what I should be doing instead.