laravel architecture comprehensive guide with real world use
I've started using laravel pretty recently. I understand the usage quite fine. Like creating controllers, working with models and views and putting them all together.
What I do not seem to understand is the complete architectural concept guide in their documentation. How and when should I make use of Service container, Service Providers, and Facades?
I simply can't stand the thought working with a giant complicated framework whose core structure I do not understand, and I've to use it like a plug and play toy...
thanks @topvillas, is it possible for your to share some resources that could help me understand the framework more better. I want to be able to make sure that when I'm writing code, I'm making the best use of the framework..
@tenmaurakashi There isn’t one way to build “architecture”. Each application will fit different architecture.
The best thing to do is to read the documentation on each component, such as service providers. As you’re building applications, you’ll see opportunities to make use of different components.
Trying to decide on something before you’ve actually built it just leads to premature optimisation and can take more time to “un-do” and fix than just re-factoring as you go along.