Skip to content
This repository has been archived by the owner on May 5, 2024. It is now read-only.

Home

Jump to bottom
brandonsavage edited this page Dec 20, 2014 · 2 revisions

Welcome to The Modus Framework documentation. This documentation outlines the way to configure and use The Modus Framework.

What is Modus?

Modus is a semi-full-stack framework for web application development written in PHP.

The idea behind Modus is not to reinvent the wheel; rather, Modus makes use of and incorporates components from other frameworks. To that end, Modus itself is made up of less than 1,200 lines of code, but is made up from 19 packages from three different frameworks plus independent packages. These packages combined hold more than 200,000 lines of code, and are extremely flexible.

Why the &^!* would you write another framework?

The simple answer is that I didn't write another framework.

Yes, Modus is a framework. But Modus, by itself, doesn't do anything; it needs the packages of other frameworks to function. In fact, Modus is largely "glue code" that holds these packages together for the purpose of making them into a full-stack framework.

For example, Monolog and BooBoo by themselves are not a framework, but combined with other packages can be part of a framework. That's what Modus does: bring these components together into a "full-stack framework."

Why should I use Modus over Symfony/Zend Framework/Laravel/Etc?

Modus has a few advantages over other frameworks:

  • Modus is 100% dependency injected. If configured correctly, you never need to instantiate an object inside the framework.
  • The Action-Domain-Responder pattern correctly addresses separation of concerns. Each action is independent; there are no monolithic controllers.
  • The separation of concerns allows you to test your application, top to bottom. Test your actions, your responders, and your domain, top to bottom, start to finish.
  • We don't make assumptions about the resources you need. You have to configure all of your dependencies; this both encourages good design (since you have to spell each dependency out) and means that unneeded dependencies are not injected into your actions or responders.
Clone this wiki locally