Why Mongo over *SQL? (Not trying to start a flame war) about swordfish HOT 3 CLOSED

I'm interested to hear about this too—more because I've not really ever worked with Mongo before than anything else.

from swordfish.

It may make sense for us encrypting items of any size. Right now it's just username/password pairs, but notes, CC info, etc may come in the future. I'm not entirely sure what @bkeepers has in mind, but I'd love to see this replace 1Password for me in the future.

from swordfish.

@asenchi As @skalnik mentions, my initial motivation was because I want items to be schema-less (could be login, credit card, software license, etc). However, the schema has become fairly static, with all the real info stored in one encrypted blob. There may be other unencrypted fields later, but there's no reason we can't serialize them into a text field.

So there's no reason it needs to stay in Mongo. I'm fine with moving it to something else if someone wants to take a stab at it.

Side note: You should all actually try building something with Mongo. It's gotten a bad rap, but I personally I prefer it to anything else right now. There are certainly tradeoffs, but there are with any database. Most don't learn about the tradeoffs and then hate on Mongo when their ignorance bites them in the ass.

from swordfish.