Skip to content
Kelly Gendron edited this page Apr 28, 2016 · 1 revision

Aurum aims to be an alternative to traditional ORMS.

Aims:

  1. Leave developers in full control of the code and queries run in the data-layer
  2. Allow code generation across multiple layers of an application
  3. Fully leverage the framework's position in the stack to warn about queries that don't match code

Design Guidelines:

  • The performance cost of using an ORM should not be paid at runtime
  • Everything should be overridable
  • Projects should not be dependent on Aurum - Removing the plugin should leave working generated code
  • When code isn't working correctly the developer should be able to debug it - no black boxes

Clone this wiki locally