search

KYOSS / kyoss-topic-manager

A web application to allow members of KYOSS to vote on topics for meetings.
Apache License 2.0
3 stars 5 forks source link

Application needs a storage system #3

Open InfoSec812 opened 10 years ago

InfoSec812 commented 10 years ago

We need to decide on a storage system... Please comment below on what and why your preference should be chosen.

InfoSec812 commented 10 years ago

I would like for something simple and preferably embedded so as to simplify running unit/integration tests. In Java or Vert.x we could use something like HSQLDB and store the default data in a CSV file within the project.

zeroasterisk commented 10 years ago

I've had no problems setting up MySQL, Postgress, Mongo, Redis, ElasticSearch on travis-ci and using a script to initialize "fixture" dataset... that said, the scope of data we need for this project IS probably quite small and maybe file storage makes it the most portable at first pass.

Ideally, we could make it backend storage agnostic, but a storage abstraction layer is one more complexity/feature to add.

All things being equal, if we are doing Vert.x, I vote we go with as simple as possible on first pass - and I don't know enough about Vert.x/Java to know what that option would be.

(I do think any of them would work for us... and mongo is REALLY simple to work with, so that's probably my 2nd option)

rsyring commented 10 years ago

SQLite?

InfoSec812 commented 10 years ago

Randy, you gotta give justification if you want to convince us!

Deven Phillips from my mobile On Jul 8, 2014 3:37 PM, "Randy Syring" notifications@github.com wrote:

SQLite?

— Reply to this email directly or view it on GitHub https://github.com/KYOSS/kyoss-topic-manager/issues/3#issuecomment-48389486 .

ghost commented 10 years ago

I second Alan's post.

InfoSec812 commented 10 years ago

@inkFlowed Which part? He mentioned like 8 different options... Also, why do you support his opinion? Please, participate and share you ideas!! :)