Skip to content
Lance Pollard edited this page Oct 16, 2012 · 1 revision

Tower is a set of interfaces (conventions) over everything you need to build an app for the client and/or server.

  • database interface
  • URL (and query param) interface
  • model interface
  • factory interface
  • fake data interface
  • rest interface
  • socket interface
  • processor interface
  • background job / queueing interface
  • platform as a service (paas) interface
  • authentication interface
  • authorization interface
  • attachment interface
  • mailer interface
  • formatting interface
  • [todo] command-line interface

So if any of the standard node libraries get replaced by better ones down the road, they can be merged into Tower without having to rewrite any code in your app. This means we can take advantage of the flexibility of using small node modules, while also making sure you're somewhat immune to change.

Tower tries not to reinvent any core functionality, but just fills in the blanks around other more powerful, more specific, libraries. It takes a lot to wire up all of those different components for every app.

Clone this wiki locally