Return-Path: X-Original-To: apmail-couchdb-marketing-archive@minotaur.apache.org Delivered-To: apmail-couchdb-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2F68017C01 for ; Tue, 5 May 2015 06:18:08 +0000 (UTC) Received: (qmail 47824 invoked by uid 500); 5 May 2015 06:18:08 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 47781 invoked by uid 500); 5 May 2015 06:18:08 -0000 Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: marketing@couchdb.apache.org Delivered-To: mailing list marketing@couchdb.apache.org Received: (qmail 47769 invoked by uid 99); 5 May 2015 06:18:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2015 06:18:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.164.171.186 which is an MX secondary for marketing@couchdb.apache.org) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2015 06:18:01 +0000 Received: from smtpdb7.aruba.it (smtpdb7.aruba.it [62.149.158.249]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTP id 6CEA04380B for ; Tue, 5 May 2015 06:17:41 +0000 (UTC) Received: from mail-oi0-f44.google.com ([209.85.218.44]) by smtpcmd03.ad.aruba.it with bizsmtp id Q6HX1q00f0y3pY1016HYl0; Tue, 05 May 2015 08:17:33 +0200 Received: by oift201 with SMTP id t201so131723968oif.3 for ; Mon, 04 May 2015 23:17:32 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.129.229 with SMTP id l98mr31358953ioi.32.1430806652285; Mon, 04 May 2015 23:17:32 -0700 (PDT) Received: by 10.107.57.193 with HTTP; Mon, 4 May 2015 23:17:32 -0700 (PDT) In-Reply-To: References: Date: Tue, 5 May 2015 08:17:32 +0200 Message-ID: Subject: Re: CouchDB Articles, Pills and Tutorials Ideas From: Giovanni Lenzi To: marketing@couchdb.apache.org Content-Type: multipart/alternative; boundary=001a113e56dc40796f05154fa23c X-Virus-Checked: Checked by ClamAV on apache.org --001a113e56dc40796f05154fa23c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable @ermouth: Seems more that you are puNChing it, instead of puShing it :) Besides the fact I don't agree, and I am not alone, with many of your concerns... I think this is exactly the kind of Stackoverflow CouchDB-killing answers, which negatively affect the project. Why can't we, at least from the inside of this community, share our positive experiences, and leave the burden of defeatism to CouchDB competitors? also considered that CouchDB, as everything else, evolves and old release limitations are no more actual and actual ones are likely to be outdated in future! > A lot, and they generally use LAMP We all come from LAMP or other stacks, but things evolve... otherwise we would be still at the stone age > Also tooling and documantation around couchapps are really, really poor =E2=80=93 you know it Yes. This was the topic :) : expanding content around CouchDB > Sure, I have quite large projects, that are built on top of CouchDB Great, would you like to write down some of your positive:-)) experiences? 2015-05-04 20:19 GMT+02:00 ermouth : > > and how many freelancers, small and medium companies are there instead? > > A lot, and they generally use LAMP. If they are more advanced =E2=80=93 M= EAN. > Couchapps are extremely rear =E2=80=93 they need way of thinking and skil= ls more > common for large serious projects. MapReduce is not the thing common for > small sites. > > Also tooling and documantation around couchapps are really, really poor = =E2=80=93 > you know it. And reason for it is not underestimation =E2=80=93 reason is= couchapps > are limited and limiting. Couchapps are too complex for simple projects a= nd > too limiting for large systems. > > Although there exist some real-life architectures, where couchapps are > integrated into large systems. For example you can have couchapp-driven > backend that serves tenths of users =E2=80=93 and full-powered frontend t= hat > employs CouchDB replicated from backend, but as DB, not as app platform. > > > I assume you like something about CouchDB, right > > Sure, I have quite large projects, that are built on top of CouchDB =E2= =80=93 but > most of them are under NDA. In fact, combining CouchDB with node.js in > front you can create distributed, reliable, fast and complex solutions th= at > fly with zero issues for years =E2=80=93 but using only couchapps you def= initely > can not. > > > ermouth > > 2015-05-04 20:44 GMT+03:00 Giovanni Lenzi : > > > I agree couchapps couldn't be used for anything, of course but... how > many > > large companies does exist? and how many freelancers, small and medium > > companies are there instead? > > > > However, I'm just giving my 2 cents to spread CouchDB here... and trust > me: > > there is a lot of interest around Couchapps. Almost all our customers u= se > > them in one way or another. > > > > Anyway, @ermouth if you are here, I assume you like something about > > CouchDB, right? If yes, is it something you can share on that list? > > > > > > > > 2015-05-04 18:44 GMT+02:00 ermouth : > > > > > >but I think Couchapps are really a game-changing feature > > > > > > They are not, it=E2=80=98s an overcomplicated, hard to debug and brit= tle > solution > > > for small projects. > > > > > > Also couchapps generally have very poor perfomance =E2=80=93 because = json > > > serialization/deserialization while transmitting data from map to _li= st > > and > > > _show functions is slow. > > > > > > > Why using a web, app and db server when you can just use CouchDB? > > > > > > Because there exist not only small projects. So we need rater, monito= r, > > > counter, cache and so on. > > > > > > ermouth > > > > > > 2015-05-04 19:10 GMT+03:00 Giovanni Lenzi : > > > > > > > > > > > > > > > > > --001a113e56dc40796f05154fa23c--