Decide on Website Framework

[MgenGlder]

Summary

• As part of setting up a new website we'll need to decide on a web framework to use for the backend serving. While looking for a framework that accomplishes what we want, we'll need to consider how robust the testing is in our selected framework. A couple ideas are listed below:

Python Options

• Django
  • Batteries included
  • More robust modelling
• Web2py
  • Simple, bare bones, fair testing framework
• CherryPy
• Flask

NodeJS Options

• ExpressJS
  • Well known, popular routing and web server framework in NodeJS.
  • Authentication / Authorization is not built in, and requires manual setup most of the time.
• MeteorJS
  • Entirely batteries included, from DB (MongoDB) compatibility.
  • Doesn't require significant middleware setup.
  • Relies heavily on the Blaze frontend framework, which is now mostly obsolete.
• KOA.js

---
title: Frontend to Backend Request Flowchart
---
flowchart TD
    note[[Note: Very early draft]]

    subgraph Backend
    B-->C(Auxilliary Backend)
    end
    A[Browser] -->|Web Request| B(Primary Backend)

[MgenGlder]

As of today, we've decided on using Django to handle our backend needs. It is suitably batteries-included and has broad community and managed service support. It also is written in Python, which our group has strong skills in so far.