(stupid?) question: replacing mongo by etcd ?

[yannick grenzinger]

Hello,

I am a finishing a project were I use mongodb for application data and etcd for configuration info (and mainly the amazing 'watch' change capability).

After some time struggling, I have finally made work a cluster and I'm asking myself why not replacing mongo by etcd.

Why ? 

Because the applicative data are mainly configuration for an "applicative" router where some user will rarely change a bunch of routing configs.

In summary,

- mainly "key/value"

- really few data and write

- lots of read by second but I need mainly resilience

- having the capability to store the data in memory and 'watch' when it change can be really effective

What do you think ?

Thanks

[Seán C. McCord]

While MongoDB and etcd are designed around very different problem sets, and it is, thus, usually not a good idea to compare or interchange them, your case sounds more suited to etcd than to MongoDB.  I think you would be fine to use etcd instead, caveat the limitations and deployment guidelines of etcd itself (which are no more onerous than a production MongoDB deployment, anyway).

--
You received this message because you are subscribed to the Google Groups "etcd-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to etcd-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Seán C McCord

CyCore Systems, Inc

+1 888 240 0308

[Seán C. McCord]

I would say, though, if you are really heavy on the reads-per-second figure, consider something like Redis instead.