> We will go through the installation process, basic setup, listen to events through the HTTP interface, and look at a simple use case of storing HTTP events into a MongoDB database.
...and I'm out.
...and I'm out.
None of the above (HTTP, MongoDB, etc...) is needed at all, you can just as well setup a logfile watcher as input, which sends the log messages over to a logfile writer on another machine, all within 5..10 minutes on 2 VMs.
Or you can directly write messages (JSON or MessagePack) to a TCP socket (MessagePack-formatted messages to TCP socket is basically the lowest level you get).
Messages have a tag for filtering and routing.
It's basically just input plugins connected to output plugins, and you build a message distribution network from that. And it is extremely easy to get into.
step2: mention mongo
step3: enjoy having the room to yourself
:-P
Also, I am giving MongoDB the benefit of the doubt per Curt Monash's law of databases:
Rule 1. It takes at least 7 years to build a database
Rule 2. You are not an exception to Rule 1.
I would still use mariadb or postgresql before mysql.
just because the big boys use it, doesn't mean it's good.
I honestly don't know if that mitigates against a lot of the MongoDB hate you see around here (including my post above). If I was at a place like Stripe and that money to pay Aphyr to battle-test all my database systems and an ops staff the handle all the issues that he found, then I could maybe deploy MongoDB successfully. I'd also have the sort of really, really hard problems that require me to spend that kind of resources on the problem. MongoDB is a much, much worse choice for those of us who DON'T have those needs and resources, though.
It's this funny situation where some engineer starts off using it because it's very convenient to run, and maybe the data model is convenient. You scale it up a bit, debug it, tune it, stuff you'd have to do with any system. At the point when you're sure mongo really sucks, it's too late. The business and even technical management side always prioritizes some other project over replacing it, even though you spend a surprising amount of time each month maintaining the mongodb cluster (performance degredation that compaction doesn't completely fix, and other stuff...).
I get the sense that with 3.0.3 or so, mongodb is a real database now. But it's been years of pain and false advertising. I'd still always vote against it. (Even though at my current place some people started using it for a service... :(