Hey Vins,
The solution is pretty integrated with MongoDB, but the only component that you would need to swap at this point is the authentication storage (in theory, one could even just store authentication details in a flat file)
Having used both MongoDB and relational systems, I find the document style that mongo uses to be more intuitive and easier to build applications on top of, since your data is returned in nicely structured hashes and embedding data can be extremely useful.
https://en.wikipedia.org/wiki/Document-oriented_database
But yes, they're pretty different and optimal schemas for each system would be different. Ultimately the choice should be dependent on application. I would encourage you to give mongo a try though, especially if you've never used it before!
In reply to Re^2: Mojolicious and MongoDB
by rahuldhodapkar
in thread Mojolicious and MongoDB
by rahuldhodapkar
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |