djikstra
be humble.
Version: 0.8.0.2.6
(Simplified...)
It Is Good To Be Humble...
The Humble Framework is all about easy application development, robust flexibility, and maintainability. It is a framework that from the start was designed to actually fight Software Entropy, and that means lower cost of maintenance and enhancements down the road. But speed of application development doesn't mean that Humble sacrifices speed of execution... quite the opposite! From its outset, Humble has been designed to scale in breadth (services) and not depth (monolithic), and this has allowed Humble to evolve and shine in the realm of MicroService Architecture Application development. On top of that, with a high degree of abstraction, support for modern JavasScript frameworks like React and Vue, while also supporting a host of server-side rendering languages like Smarty, Twig, Mustache, etc... whatever your needs are, it is likely that Humble can fill them.

Some Key Features of Humble...
MVC
Humble is a Model-View-Controller framework where the Controllers are XML files, the Models can be written in PHP or implied (more on that later), and for the Views, there is support for modern JavaScript libraries (i.e. Angular, React, or Vue) or server side rendering using any templating library you'd like (i.e. Twig, Smarty, Mustache, etc...)
Design More, Write Less
At its heart, Humble uses an Event-Driven model that can trigger graphically designed workflows. These workflows are composed of model objects that are cataloged and categorized as developers build them, creating a "Lego" style architecture. Events can be User driven (such as form submission), Time/Date events for recurring daily, weekly, or monthly processes, or system events such as the arrival of files or other autonomous event.
Polyglot ORM
Humble uses the Unity Polyglot ORM, which combines the functionality of MySQL and MongoDB. This combination makes it easy to add columns on the fly, store hierarchical data alongside traditional schema based entities, keep the concept of Normalization and Joins while leveraging "Big-Data" features, and solves problems elegantly that used to require obtuse approaches like EAV (Entity-Attribute-Value).
Integration Abstraction
For the last 20 years, for an application to be "Enterprise" class it had to be able to integrate, both as a Producer and a Consumer, with external sources of functionality and data. Gone are the days of the "One-Big-App". Humble makes integration a feature of configuration, not coding, by abstracting Integration Points using YaML files to define the features of those Integration Points. Also, through the Paradigm Engine Workflow Editor, you can easily create an ESB (Enterprise Service Bus) that can broker the data you wish to share with others. Integration is integral to today's connected world, and is at the heart of the Humble framework.
Easy Transition from Monolith to MicroService Architecture
Develop your application as a monolith but when you are ready for production, you can deploy it as a multi-server MicroService Architecture (MSA) application, with no specialized coding required. Because Humble uses exceptionally "clean" URIs, the namespace component of each URI can be mapped to a dedicated server to handle all requests specific to that namespace. Then all we need to do is to designate one of the server "nodes" to be the MSA Router, and we can leverage the scalability and reliability that is native to MSA applications. This phase of development/deployment is referred to as "MicroService Mode", but it is so simple to effect that it might as well be called "Magic Mode".