Laravel 4 Route::dispatch overhead

Question

I'm working on a web application that need to expose Json API for external apps and I'm planning to do an API centric architecture.

So basicly, the app will juste contains view/controllers for the web interface. the controllers will use Route::dispatch to create a request to the api part of the site (another controller in a package, but in the same laravel installation), then parse the result, and create view accordingly.

So I'm wondering what are the drawbacks, performance wise, of using this sort of architecture?

Answer 1

If each controller is writing the logic to internally dispatch another request then I'd consider abstracting that away from the controller and in to your own dispatcher. I doubt there would be a huge performance overhead. The application (as far as I know) doesn't get booted twice so you don't have to worry about that.

The only thing you need to be aware of is the input for the main request being used. Something you should take into account inside your dispatcher. Refer to this answer for more information.

You can also read more on consuming your own API .