Sahana Framework Evaluation

This page has been reformatted. The previous discussion was archived here for reference.


Throughout early 2010 the Sahana Community has engaged in an open discussion of potential frameworks for future program development. To facilitate and document this discussion a group of pages has been created.

We invite anyone with relevant information to share it with the Community. To ensure documentation that is both detailed and easy to read, we ask you to use the Framework Evaluation Template for any new framework pages.

If you would like to provide details on a framework that has already been introduced to the discussion, please see the Potential Frameworks category below.


Host a structured discussion within the Sahana community to evaluate PHP frameworks for future Sahana development.

Framework Requirements

This section is intended to document high level requirements for potential frameworks. They are organized by relevant categories and you're encouraged to add your own.

Wiki Best Practises Please keep these tips in mind when adding new criteria:

  • Categorize the requirement
  • Link to an external site for additional information if relevant or necessary
  • Add additional details for any generic or easily mis-interpreted terms.

Feel free to copy this text and use it to add any new categories:

===== Category Header (name your new category here) =====
  * Describe the essentials of this category using two spaces and a bullet point
    * For bullets with more detail just use two additional spaces at the beginning


  • Database Engine Support
  • ORM Engine Support
  • Object Views
  • Transaction History with rollback
  • Auditing and Statistics
  • Custom Data Types
  • Triggers and constraints


  • Error Handling/Exception Handling
    • Uniform Exception Framework
    • Proper/Standard Error Codes
      • Transparency
      • Verbosity easily transfigurable
  • QA/Testing
    • Usability/integration testing
    • Custom test definition
    • Integration (automation)


  • External (by the framework's community)
    • Quality
    • Depth/Expansiveness (How detailed is it?)
    • Are their published reference texts?
    • How current is the documentation?
      • Integration on framework developers site
    • Wiki generation
  • Internal (within the framework itself)
    • Function/API documentation auto-generation
    • Generated code has meaningful in line documentation


  • Security
    • Framework's community supports an independent security team
    • Long term support and highly stable framework versions offered
    • Framework's security patches offered without requiring version upgrades or breaking API
  • Testing
    • Support for 3rd party validation tools
    • Built in code validation (ex. pen testing)
    • ACL support/library
    • Server security integration with 3rd party authorization (ex. Apache)


  • Standards Validation Library
    • ISO
    • IEEE
    • W3C compliance
      • XML
      • XHTML (version & strictness)
      • WCAG
      • Other
    • Other standards bodies
    • Custom validation library support (eg, Regex)
    • Code sanitation
  • Modularity
    • Ease of development of modular applications
    • Supports template modules for rapid development of additional modules
    • Ability enable / disable independent of removal
    • Versioning & compatibility support (eg, works with Sahana v 1.0 –> 1.5.x)
    • Upgradability
  • Client support
    • Browser support
    • Graceful Degradation (ex: browser with no javascript or other libraries)
    • Not dependent on AJAX
  • Web Services
    • SOAP
    • JSON
    • ATOM
    • REST
      • Community support & interest in RESTful services & API
    • RSS
    • Custom
  • Geospacial Capabilities
    • Standards
    • Engines
    • Modular data abstraction (multiple dbs for different purposes)
    • 3rd party data provider support
  • Database Migration/Upgrade
    • Features
    • How does it compare to Rails RAKE?
  • Templating
    • Support for multiple template engines
    • Support for a number of pre-defined template styles within a single app
    • Ease of development of templates
    • Template inheritance (do changes to parent templates reflect in the children)
    • Template flexibility
  • Performance
    • Statistics & conclusions
    • Test bed specification
    • Relevant software versions
    • Date of testing
    • Tester / reporter
  • Scalability
    • Statistics & conclusions
    • Test bed specification
    • Relevant software versions
    • Date of testing
    • Tester / report


  • Caching features
  • Indexing
    • Automatic / trained index features
    • Manual tuning
  • Options for pre-computing data
  • Other efficiency features


  • Requirements
    • Resource requirements
    • Complexity/Skill level required
    • Tools / libraries needed for installation
    • Packaging
    • How are updates handled?
    • Language Support
  • Out-of-box OS support
    • Red-Hat
    • Ubuntu Server LTS
    • Suse Linux Enterprise Server
    • Windows Server 2008
  • Licensing

Potential Frameworks

Each of these pages links to a potential frameworks evaluation page stub. Please feel free to flesh out the page for any framework that you have tested or have knowledge of to facilitate conversation with the rest of the Community.

If you would like to add an additional framework for discussion, please use this template to ensure consistency.


Please feel free to use this section for discussion and comments. Be sure to sign your post using the button all the way to the right on the menu above. Also, please do not remove anyone else's relevant comments.

QR Code
QR Code dev:fk_requirements (generated for current page)