So I'm currently developing the backend for a new system I have in mind. As part of this, I need to include a fake currency. Users will be able to get them from the "bank" as trade ins. Every user may have multiple accounts, transactions may take place between any accounts.
So I basically have to setup a simple banking data model to accommodate my needs, as the total of available currency should never change.
I cannot decide whether to implement this using an enterprise data model or go full retard and use a dimensional model.
What's your opinion on this, /g/? What would you use? Underlying database may be MongoDB, but I haven't made a final decision yet...
>>57233329
>Underlying database may be MongoDB
>>57233343
> constructive feedback is constructive
> mfw /g/ can't answer a simple CS-degree data modelling question
>>57233553
>>57233553
/g/ is full of headphone hipsters, kids and 'muh c, Haskell and Lisp' sperg Lords. Dont be coming here expecting help with serious Software development questions
>mongodb
>>57233553
but you can't either.
>Want to use non-relational database
>Data is relational
Dude
>>57235218
Dont worry, i wont. This is a cesspool
>>57235257
>but I haven't made a final decision yet...
>what is constructive criticism
Jerk off to your 2d waifu and get out nigger
>>57235307
>mongodb
>>57235304
> may be MongoDB
> may be
> may
>>57235307
it's just really weird that you're going to have a database of relational data and then go for a solution that excludes that model
>>jerk off to your 2d waifu
>posts anime picture
kys
>>57235348
Agreed. The fact that it was even considered raises substantial questions.
We use mongo at work but that's because there is a lot of data and it is legit not relational.
>mongodb