What is the Mach II framework's mission? - Mach-II/Mach-II-Framework GitHub Wiki
Mach-II's place in the framework landscape is as an application development framework as opposed to an Object-Relational Mapping (ORM) framework like Reactor, or an Inversion of Control (IoC) framework such as ColdSpring. The mission of Mach-II is to do MVC and do that well without sacrificing extensibility. Mach-II is highly extensible through its filter and plugin architecture. This design allows you to leverage third-party functionality or other frameworks easily. For example, Mach-II ships with a ColdspringProperty CFC that enables seamless integration between the two frameworks.
A by-product of this basic credo is that Mach-II is not hampered by the release schedules or bugs of other frameworks because they are not intrinsically integrated into the Mach-II core. This allows Mach-II developers to "virtually customize" Mach-II so your application always have your architecture and specifications without being forced to abide by convention over configuration.
For more information, read our wiki entry on Mach-II's Project Philosophy