Home/ Questions/Q 7923801
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T17:25:57+00:00

I’m using a traditional Zend framework application generated using Zend tool . I have

  • 0

I’m using a traditional Zend framework application generated using Zend tool. I have several modules in my application all generated using Zend tool too. I’m intending to use the default routes in Zend framework in my application.

For example: www.host.com/module/controller/action/param1/value1/param2/value2

Here are my questions:

  1. Performance wise, using the default routes is the fastest solution, right?
  2. Since I won’t ever change the routes, is there a way to make the
    routing process even faster? caching for example? skipping the routing
    process entirely? or any other technique?
  3. What is the pros of making custom routes? is it better for SEO?
  4. Can I skip the routing process for AJAX calls? (I know the answer
    is mostly NO, but maybe I can optimize my call further for AJAX calls)

Note:

I understand the routing process itself and how it works in Zend
framework. However, since I won’t be using most of the features
available I thought maybe it’s time for fine tuning 🙂

Thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    1 . Performance wise, using the default routes is the fastest solution, right?

    Right, but not using any routing system is the fastest solution (obviously).

    2 . Since I won’t ever change the routes, is there a way to make the routing process even faster? caching for example? skipping the routing
    process entirely? or any other technique?

    Well, that’s the thing, routes are mostly used for flexibility, internationalization, SEO.

    The problem with the Zend Framework Router is that it depends and wraps the Front Controller instance, therefore it is hard (well impossible afaik) to cache the Router since the FC itself wraps others things like PDO instances which are not cachable.

    So all routes are computed again and again for every requests.

    A possible solution when using complex routes while avoiding route computation is to dump all routes to native Apache Rewrite Rules, it will be blazing fast compared to ZF, the main problem with this solution is that you need to manually compute reverse routes and whenever you make a change to a route, you’ll need to edit it by hand.

    As often, it is scalability vs performance.

    3 . What is the pros of making custom routes? is it better for SEO?

    Well, it “depends” ™:

    /list?type=products vs /products, the second route wins.

    However, /products/page/1 vs /products?page=1 is a win-win (well it actually does not but it is another story).

    Other pros:

    • i18n
    • seo
    • usability
    • meaningful url

    4 . Can I skip the routing process for AJAX calls? (I know the answer is mostly NO, but maybe I can optimize my call further for AJAX calls)

    I don’t see any cons against this. I often go for it, except for RESTfull API.

    • 0