Do we always need MVC?


One thing that users of frameworks like CodeIgniter know is MVC architecture - Models, Views, and Controllers. Quite often the framework has setup an app structure that reflects this, and so tutorials and user guides leave the impression that we should organize our application that way. But is this always the best way?

I got to thinking about this recently while refactoring Bonfire. At one point, mainly due to frustrations with the refactoring progress, I started moving things to a little bit more traditional structure, pulling some files out of the Modules folders they were contained within and putting them…

Members Only

This post is only available to Patrons. If you are a Patron, please login.


Not a member, yet?

You can join now for less than the price of two coffees a month!

Membership has its benefits:

  • Can read all of the articles (like this one)
  • Access to a growing library of video courses
  • and more coming soon!
Become a Member
About the Author

Lonnie Ezell is a programmer, author, musician, spouse, and father. He is the lead developer on CodeIgniter 4, and Bonfire--an admin framework for CodeIgniter 3 and now 4. He has written two books on CodeIgniter, and ran a popular Tabletop RPG podcast for several years.


You must be logged in via Patreon to leave a comment.