acm-uiuc/groot-api-gateway

Stack for Groot

Closed this issue · 6 comments

narendasan commented

Current ideas Node, Express, Mongoose, Backbone, sass, skeleton

sskhandek commented

Adding in Mongo, Angular, Foundation

narendasan commented

There has been multiple people who want to use flask instead of node @mathur @QLPSCO

achalv commented

I don't think Flask is quite robust enough for the kind of stuff we want to
accomplish with and for this project, but that's just my $0.02.
On Sat, Apr 25, 2015 at 7:46 PM Naren Dasan notifications@github.com
wrote:

There has been multiple people who want to use flask instead of node

—
Reply to this email directly or view it on GitHub
acm-uiuc/groot#4 (comment).

colegleason commented

I would advise against Mongo. It would be nice to keep all of this data on
DBs that Admin maintains. Plus, it all seems like relational data.

On Sat, Apr 25, 2015, 9:25 PM Achal Varma notifications@github.com wrote:

I don't think Flask is quite robust enough for the kind of stuff we want to
accomplish with and for this project, but that's just my $0.02.
On Sat, Apr 25, 2015 at 7:46 PM Naren Dasan notifications@github.com
wrote:

There has been multiple people who want to use flask instead of node

—
Reply to this email directly or view it on GitHub
acm-uiuc/groot#4 (comment).

—
Reply to this email directly or view it on GitHub
acm-uiuc/groot#4 (comment).

achalv commented

I agree – We shouldn't deviate from existing data infra too much. I'm for using Mongo for new services we're building alongside Groot, but let's use DBs that Admin is currently maintaing for other stuff. Less overhead.

narendasan commented

What about using dartlang?