On Thu, Sep 9, 2010 at 11:14 AM, TiagoP <pix...@gmail.com> wrote: > Hi,
> Which database do you usually use with your node.js projects? Is there > any that fits node better? Maybe Riak?
> -- > You received this message because you are subscribed to the Google Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
On Thu, Sep 9, 2010 at 6:16 PM, James Carr <james.r.c...@gmail.com> wrote: > I always use couchDB, but the real answer is highly subjective.
> I'd say: go with what you are most comfortable with.
> Thanks, > James
> On Thu, Sep 9, 2010 at 11:14 AM, TiagoP <pix...@gmail.com> wrote: >> Hi,
>> Which database do you usually use with your node.js projects? Is there >> any that fits node better? Maybe Riak?
>> -- >> You received this message because you are subscribed to the Google Groups "nodejs" group. >> To post to this group, send email to nodejs@googlegroups.com. >> To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
I don't think any one is "better" then the other, however I find
myself using MongoDB for a lot of things. Fast, flexible, and the
community support is top notch as well as the documentation.
Additionally they have drivers for just about any language.
Regards,
-Josh
On Sep 9, 12:14 pm, TiagoP <pix...@gmail.com> wrote:
Seriously though, it all depends on the needs of the application and personal preference. There's not really any "ideal" database, but certainly there is some that are more suitable than others.
On Thu, Sep 9, 2010 at 9:32 AM, JoshK <josh.k...@gmail.com> wrote: > I don't think any one is "better" then the other, however I find > myself using MongoDB for a lot of things. Fast, flexible, and the > community support is top notch as well as the documentation.
> Additionally they have drivers for just about any language.
> > Which database do you usually use with your node.js projects? Is there > > any that fits node better? Maybe Riak?
> -- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en.
> Seriously though, it all depends on the needs of the application and
> personal preference. There's not really any "ideal" database, but certainly
> there is some that are more suitable than others.
> On Thu, Sep 9, 2010 at 9:32 AM, JoshK <josh.k...@gmail.com> wrote:
> > I don't think any one is "better" then the other, however I find
> > myself using MongoDB for a lot of things. Fast, flexible, and the
> > community support is top notch as well as the documentation.
> > Additionally they have drivers for just about any language.
> > > Which database do you usually use with your node.js projects? Is there
> > > any that fits node better? Maybe Riak?
> > --
> > You received this message because you are subscribed to the Google Groups
> > "nodejs" group.
> > To post to this group, send email to nodejs@googlegroups.com.
> > To unsubscribe from this group, send email to
> > nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/nodejs?hl=en.
Every job has different requirements for completion. To say technology X is best is oversimplifying the problem. It doesn't take into consideration the skill set of your developers, what tools your currently using nor learning curve or costs of switching to said technology. Picking any technology is always a battle of compromises. One team might pick a cutting edge solution because it makes their development faster while another team may pick another because documentation and community support is more complete. Neither one is wrong. Pick the solution that gives your team the least tradeoffs for your existing development process.
On Thu, Sep 9, 2010 at 10:32 AM, ono <pix...@gmail.com> wrote: > Can you elaborate on that last part? thanks
> On Sep 9, 6:20 pm, Stephen Belanger <cyruzdr...@gmail.com> wrote: > > This thread is giving me deja vu.
> > Seriously though, it all depends on the needs of the application and > > personal preference. There's not really any "ideal" database, but > certainly > > there is some that are more suitable than others.
> > On Thu, Sep 9, 2010 at 9:32 AM, JoshK <josh.k...@gmail.com> wrote: > > > I don't think any one is "better" then the other, however I find > > > myself using MongoDB for a lot of things. Fast, flexible, and the > > > community support is top notch as well as the documentation.
> > > Additionally they have drivers for just about any language.
> > > > Which database do you usually use with your node.js projects? Is > there > > > > any that fits node better? Maybe Riak?
> > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "nodejs" group. > > > To post to this group, send email to nodejs@googlegroups.com. > > > To unsubscribe from this group, send email to > > > nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> > <nodejs%2Bunsubscribe@googlegroups.com<nodejs%252Bunsubscribe@googlegroups. com>
> -- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en.
Just wondering, in what situations (application for example) would you say MongoDB is a better choice than CouchDB? I'm just starting NodeJS development so it'd be great to hear some of your experiences.
Cheers
On Thu, Sep 9, 2010 at 10:20 AM, Stephen Belanger <cyruzdr...@gmail.com>wrote:
> Seriously though, it all depends on the needs of the application and > personal preference. There's not really any "ideal" database, but certainly > there is some that are more suitable than others.
> On Thu, Sep 9, 2010 at 9:32 AM, JoshK <josh.k...@gmail.com> wrote:
>> I don't think any one is "better" then the other, however I find >> myself using MongoDB for a lot of things. Fast, flexible, and the >> community support is top notch as well as the documentation.
>> Additionally they have drivers for just about any language.
>> > Which database do you usually use with your node.js projects? Is there >> > any that fits node better? Maybe Riak?
>> -- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To post to this group, send email to nodejs@googlegroups.com. >> To unsubscribe from this group, send email to >> nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en.
On Thu, Sep 9, 2010 at 7:42 PM, nwhite <changereal...@gmail.com> wrote: > One team might pick a cutting edge solution > because it makes their development faster while another team may pick > another because documentation and community support is more complete. > Neither one is wrong.
For the sake of discussion, I disagree with that. Betting on the wrong technology will bite you hard, even if it gets you quickly to an working product (but I don't think it would).
Speaking of languages: judging by community, PHP is still the "superior" choice. But you don't want to use PHP, really.
Speaking of databases, again judging by the community size, MySQL seems to be the winner. But with it, you'll lose.
See, speaking in general, the tools that manage to attract the biggest communities are usually the crappiest ones. I'm not sure why this happens, but it does. We're living in a "worse is better" world. [1]
> Which database do you usually use with your node.js projects? Is there > any that fits node better? Maybe Riak?
> -- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en.
I should let someone else answer that, I looked at both when I started on my current node projects, but ultimately went with Mongo. I haven't actually * used* couch though, so I wouldn't exactly consider that a reliable judgement to go by. I'd recommend taking the time to research whatever options you are considering until you can make the choice yourself. Then you can only blame yourself if difficulties arise at some later point.
On Thu, Sep 9, 2010 at 10:25 AM, Jaime Bueza <jbu...@gmail.com> wrote: > @Stephen
> Just wondering, in what situations (application for example) would you say > MongoDB is a better choice than CouchDB? I'm just starting NodeJS > development so it'd be great to hear some of your experiences.
> Cheers
> On Thu, Sep 9, 2010 at 10:20 AM, Stephen Belanger <cyruzdr...@gmail.com>wrote:
>> This thread is giving me deja vu.
>> Seriously though, it all depends on the needs of the application and >> personal preference. There's not really any "ideal" database, but certainly >> there is some that are more suitable than others.
>> On Thu, Sep 9, 2010 at 9:32 AM, JoshK <josh.k...@gmail.com> wrote:
>>> I don't think any one is "better" then the other, however I find >>> myself using MongoDB for a lot of things. Fast, flexible, and the >>> community support is top notch as well as the documentation.
>>> Additionally they have drivers for just about any language.
>>> > Which database do you usually use with your node.js projects? Is there >>> > any that fits node better? Maybe Riak?
>>> -- >>> You received this message because you are subscribed to the Google Groups >>> "nodejs" group. >>> To post to this group, send email to nodejs@googlegroups.com. >>> To unsubscribe from this group, send email to >>> nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/nodejs?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To post to this group, send email to nodejs@googlegroups.com. >> To unsubscribe from this group, send email to >> nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en.
If it helps you, I used to use CouchDB, than I dropped it for Tokyo
Cabinet served by Tokyo Tyrant (with my own Lua extensions to add set
union and intersection support). I was happy with that. Then I
realized that Redis provides built-in sets, sorted sets, lists, union,
intersection etc. and it is evented, so I've just started using that
and I can say that I'm learning alot from the ideas implemented in it.
Basically Redis is NOT a key/value store, it's more like a data
structures service. You can create tries, queues, etc. in there, use
it for pub/sub, etc. Because of this focus on data structures, it has
pure and simple interfaces (similar to Tokyo). Redis makes sense in
terms of "turtles all the way down".
On Sep 9, 6:14 pm, TiagoP <pix...@gmail.com> wrote:
Not Node-specific, but this blog entry might be helpful as it attempts
to characterize some of the available NoSQL options (there's more
discussion in the comments):
we also use couchdb - but really you need to pick the db whose features fit your needs the best - at least several have a good node driver (mysql, sqlite, postgres, mongo, ....
> On Thu, Sep 9, 2010 at 6:16 PM, James Carr<james.r.c...@gmail.com> wrote: >> I always use couchDB, but the real answer is highly subjective.
>> I'd say: go with what you are most comfortable with.
>> Thanks, >> James
>> On Thu, Sep 9, 2010 at 11:14 AM, TiagoP<pix...@gmail.com> wrote: >>> Hi,
>>> Which database do you usually use with your node.js projects? Is there >>> any that fits node better? Maybe Riak?
>>> -- >>> You received this message because you are subscribed to the Google Groups "nodejs" group. >>> To post to this group, send email to nodejs@googlegroups.com. >>> To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. >>> For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups "nodejs" group. >> To post to this group, send email to nodejs@googlegroups.com. >> To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
We moved away from couchdb to redis because couchdb was too limiting for us. Redis is really nice. You can think of it as a low level database engine without the SQL cruft on top of it. For another project I tried to use MySQL but I couldn't find drivers of sufficient quality. I don't know if that has changed sine then.
On Fri, Sep 10, 2010 at 3:40 AM, MilesTogoe <miles.to...@gmail.com> wrote: > On 09/09/2010 09:19 AM, fuzzy spoon wrote:
>> What fits the job?
>> Also, i use couch as well.
> we also use couchdb - but really you need to pick the db whose features fit > your needs the best - at least several have a good node driver (mysql, > sqlite, postgres, mongo, ....
>> On Thu, Sep 9, 2010 at 6:16 PM, James Carr<james.r.c...@gmail.com> wrote:
>>> I always use couchDB, but the real answer is highly subjective.
>>> I'd say: go with what you are most comfortable with.
>>> Thanks, >>> James
>>> On Thu, Sep 9, 2010 at 11:14 AM, TiagoP<pix...@gmail.com> wrote:
>>>> Hi,
>>>> Which database do you usually use with your node.js projects? Is there >>>> any that fits node better? Maybe Riak?
>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "nodejs" group. >>>> To post to this group, send email to nodejs@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> nodejs+unsubscribe@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/nodejs?hl=en.
>>> -- >>> You received this message because you are subscribed to the Google Groups >>> "nodejs" group. >>> To post to this group, send email to nodejs@googlegroups.com. >>> To unsubscribe from this group, send email to >>> nodejs+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/nodejs?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en.
Any performance or any benchmarking which comparing for Redis,
MongoDb, CouchDb and Riak?
I know Mongo is faster than Redis and CouchDb. But lack of data for
Riak.
Also, I am looking for Pure JS Library which can store data in HTML5
Local Storage offline and sync with one of the above Db.
That will be a very nice platform for offline web app.
Eric Fong
On Sep 10, 3:33 pm, Fabian Jakobs <fabian.jak...@web.de> wrote:
> We moved away from couchdb to redis because couchdb was too limiting
> for us. Redis is really nice. You can think of it as a low level
> database engine without the SQL cruft on top of it. For another
> project I tried to use MySQL but I couldn't find drivers of sufficient
> quality. I don't know if that has changed sine then.
> Best Fabian
> On Fri, Sep 10, 2010 at 3:40 AM, MilesTogoe <miles.to...@gmail.com> wrote:
> > On 09/09/2010 09:19 AM, fuzzy spoon wrote:
> >> What fits the job?
> >> Also, i use couch as well.
> > we also use couchdb - but really you need to pick the db whose features fit
> > your needs the best - at least several have a good node driver (mysql,
> > sqlite, postgres, mongo, ....
> >> On Thu, Sep 9, 2010 at 6:16 PM, James Carr<james.r.c...@gmail.com> wrote:
> >>> I always use couchDB, but the real answer is highly subjective.
> >>> I'd say: go with what you are most comfortable with.
> >>> Thanks,
> >>> James
> >>> On Thu, Sep 9, 2010 at 11:14 AM, TiagoP<pix...@gmail.com> wrote:
> >>>> Hi,
> >>>> Which database do you usually use with your node.js projects? Is there
> >>>> any that fits node better? Maybe Riak?
> >>>> --
> >>>> You received this message because you are subscribed to the Google
> >>>> Groups "nodejs" group.
> >>>> To post to this group, send email to nodejs@googlegroups.com.
> >>>> To unsubscribe from this group, send email to
> >>>> nodejs+unsubscribe@googlegroups.com.
> >>>> For more options, visit this group at
> >>>>http://groups.google.com/group/nodejs?hl=en.
> >>> --
> >>> You received this message because you are subscribed to the Google Groups
> >>> "nodejs" group.
> >>> To post to this group, send email to nodejs@googlegroups.com.
> >>> To unsubscribe from this group, send email to
> >>> nodejs+unsubscribe@googlegroups.com.
> >>> For more options, visit this group at
> >>>http://groups.google.com/group/nodejs?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "nodejs" group.
> > To post to this group, send email to nodejs@googlegroups.com.
> > To unsubscribe from this group, send email to
> > nodejs+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/nodejs?hl=en.
Don't go the route of using LocalStorage. There is no indication that
browser vendors plan on implementing UI to enable the user to extend
the storage limits imposed on LocalStorage (currently 10mb I think).
In any event, I am under the impression that WebKit synchronously
loads LocalStorage into memory the first that LocalStorage is used, so
this would severely affect the UI if you put too much data in there. I
know from personal experience with the above issues.
Better to go with WebKit's SqlDatabase API, and implement a wrapper on
this to give you a key/value store with basic indexing. Then be ready
for Mozilla's IndexedDB, and include this in your wrapper when
IndexedDB is released.
On Sep 10, 11:53 am, Eric Fong <eri...@gmail.com> wrote:
> Also, I am looking for Pure JS Library which can store data in HTML5
> Local Storage offline and sync with one of the above Db.
> That will be a very nice platform for offline web app.
Opera has dialogs to control per site quota, btw I use the local Storage and couch together, its mainly just a save-in-case and commit to db later.
//semi topic I i decided to write a super entry level post about couch. http://blog.owned.co.za/?p=269 Ill be refining it over the course of tonight, suggestions welcome :)
On Fri, Sep 10, 2010 at 2:21 PM, Joran Greef <jorangr...@gmail.com> wrote: > Don't go the route of using LocalStorage. There is no indication that > browser vendors plan on implementing UI to enable the user to extend > the storage limits imposed on LocalStorage (currently 10mb I think). > In any event, I am under the impression that WebKit synchronously > loads LocalStorage into memory the first that LocalStorage is used, so > this would severely affect the UI if you put too much data in there. I > know from personal experience with the above issues.
> Better to go with WebKit's SqlDatabase API, and implement a wrapper on > this to give you a key/value store with basic indexing. Then be ready > for Mozilla's IndexedDB, and include this in your wrapper when > IndexedDB is released.
> On Sep 10, 11:53 am, Eric Fong <eri...@gmail.com> wrote: >> Also, I am looking for Pure JS Library which can store data in HTML5 >> Local Storage offline and sync with one of the above Db. >> That will be a very nice platform for offline web app.
>> Eric Fong
> -- > You received this message because you are subscribed to the Google Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
On Fri, Sep 10, 2010 at 2:53 AM, Eric Fong <eri...@gmail.com> wrote: > I know Mongo is faster than Redis.
With all due respect, you may want to re-check your facts... given that Redis is an in-memory datastore I find this highly unlikely. Comparing Redis to MongoDB, Couch and Riak is like comparing apples to baseballs. The only benchmark I can find to support this is http://milancermak.posterous.com/benchmarking-tornados-sessions-0 and it seems pretty flawed.
> On Fri, Sep 10, 2010 at 2:53 AM, Eric Fong <eri...@gmail.com> wrote:
> > I know Mongo is faster than Redis.
> With all due respect, you may want to re-check your facts... given > that Redis is an in-memory datastore I find this highly unlikely. > Comparing Redis to MongoDB, Couch and Riak is like comparing apples to > baseballs. The only benchmark I can find to support this is > http://milancermak.posterous.com/benchmarking-tornados-sessions-0 and > it seems pretty flawed.
> -- > Orlando Vazquez
> -- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en.
> but don't forget, no matter which db you use: vim is the best editor ever
> (just thought I'd take us off track before this goes into a flame war)
> On Fri, Sep 10, 2010 at 10:46 AM, Orlando Vazquez <ovazq...@gmail.com> wrote: > On Fri, Sep 10, 2010 at 2:53 AM, Eric Fong <eri...@gmail.com> wrote:
> > I know Mongo is faster than Redis.
> With all due respect, you may want to re-check your facts... given > that Redis is an in-memory datastore I find this highly unlikely. > Comparing Redis to MongoDB, Couch and Riak is like comparing apples to > baseballs. The only benchmark I can find to support this is > http://milancermak.posterous.com/benchmarking-tornados-sessions-0 and > it seems pretty flawed.
> -- > Orlando Vazquez
> -- > You received this message because you are subscribed to the Google Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
I've never been a fan of vim. I'm generally editing enough files at once, that a tabbed editor ends up being more efficient for me. Even for editing system files I don't tend to use it, I usually prefer to use nano.
On the note of Mongo being faster than Redis;
Really? Where did you get that idea? I was under the impression that Redis was much faster. I can't think of any particular situations where Mongo would be faster. I wouldn't really compare them though. I think they can be complimentary in many projects, having Redis function somewhat like memcache to store frequently accessed data.
> but don't forget, no matter which db you use: vim is the best editor ever
> (just thought I'd take us off track before this goes into a flame war)
> On Fri, Sep 10, 2010 at 10:46 AM, Orlando Vazquez <ovazq...@gmail.com>wrote:
>> On Fri, Sep 10, 2010 at 2:53 AM, Eric Fong <eri...@gmail.com> wrote:
>> > I know Mongo is faster than Redis.
>> With all due respect, you may want to re-check your facts... given >> that Redis is an in-memory datastore I find this highly unlikely. >> Comparing Redis to MongoDB, Couch and Riak is like comparing apples to >> baseballs. The only benchmark I can find to support this is >> http://milancermak.posterous.com/benchmarking-tornados-sessions-0 and >> it seems pretty flawed.
>> -- >> Orlando Vazquez
>> -- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To post to this group, send email to nodejs@googlegroups.com. >> To unsubscribe from this group, send email to >> nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com<nodejs%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en.
> I've never been a fan of vim. I'm generally editing enough files at once, that a tabbed editor ends up being more efficient for me. Even for editing system files I don't tend to use it, I usually prefer to use nano.
> On the note of Mongo being faster than Redis;
> Really? Where did you get that idea? I was under the impression that Redis was much faster. I can't think of any particular situations where Mongo would be faster. I wouldn't really compare them though. I think they can be complimentary in many projects, having Redis function somewhat like memcache to store frequently accessed data.
> On Fri, Sep 10, 2010 at 9:53 AM, Joshua Kehn <josh.k...@gmail.com> wrote: > All hail VIM!
>> but don't forget, no matter which db you use: vim is the best editor ever
>> (just thought I'd take us off track before this goes into a flame war)
>> On Fri, Sep 10, 2010 at 10:46 AM, Orlando Vazquez <ovazq...@gmail.com> wrote: >> On Fri, Sep 10, 2010 at 2:53 AM, Eric Fong <eri...@gmail.com> wrote:
>> > I know Mongo is faster than Redis.
>> With all due respect, you may want to re-check your facts... given >> that Redis is an in-memory datastore I find this highly unlikely. >> Comparing Redis to MongoDB, Couch and Riak is like comparing apples to >> baseballs. The only benchmark I can find to support this is >> http://milancermak.posterous.com/benchmarking-tornados-sessions-0 and >> it seems pretty flawed.
>> -- >> Orlando Vazquez
>> -- >> You received this message because you are subscribed to the Google Groups "nodejs" group. >> To post to this group, send email to nodejs@googlegroups.com. >> To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups "nodejs" group. >> To post to this group, send email to nodejs@googlegroups.com. >> To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com. > To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
Seriously people, its not about "what fits NODE", look at what you are trying to do and pick the best database for your project... some DBs focus on speed over data reliability, some on reliability over speed, etc etc.. whats best for one is not always best for another... learn it, live it, and let this pointless thread die already.
