Re: Mojolicious and MongoDB

I just started playing with Mojolicious recently. I have no MongoDB experience but have a Mojo / SQLite demo working so I could learn.

How tightly integrated is your solution with MongoDB? I assume if it was using something like DBD::driver, one could easily swap. How hard would it be to add / swap for SQLite support?

Or is there something fundamentally different about SQLite and MongoDB that I'm just not aware of with my extremely limited exposure to any type of database programming / integration?

Comment on Re: Mojolicious and MongoDB

Replies are listed 'Best First'.
Re^2: Mojolicious and MongoDB by rahuldhodapkar (Initiate) on Sep 10, 2015 at 19:21 UTC
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!	[reply]

Replies are listed 'Best First'.

Re^2: Mojolicious and MongoDB
by rahuldhodapkar (Initiate) on Sep 10, 2015 at 19:21 UTC

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!

[reply]