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 B280B11EA2 for ; Thu, 18 Sep 2014 07:45:42 +0000 (UTC) Received: (qmail 83044 invoked by uid 500); 18 Sep 2014 07:45:42 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 83006 invoked by uid 500); 18 Sep 2014 07:45:42 -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 82989 invoked by uid 99); 18 Sep 2014 07:45:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2014 07:45:42 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.82.172] (HELO mail-we0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2014 07:45:16 +0000 Received: by mail-we0-f172.google.com with SMTP id u56so28298wes.3 for ; Thu, 18 Sep 2014 00:45:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=P//QjV7WZLVL2GaXamw4VMZRcaJzrYwVu1f45azEaSw=; b=cbg4AqVVlF8WpfSDplcFZbai4GDeVW+TNm/Tl4sPHQi58MdEVe/aQ8dsQaAXEWe89h L88b/YzXBdhY0T7ui0kT/P1tnpJ9BWbp7tK75NDv9q4xUBFIVh9617BCtYSeetRhbekF zENNJ9SfhGxr8AzC+pZMgLn0dQe+0FyLJ3hCrYtXVOhFperAdim41tLvhFPaI0BQmG7a FNCI/8Yo2F6Hl5cwwvu2j7JaGe52CHML5QE1D3lAz6Ioi9MQyBBGQqiY4EKdXi1wu3ks 0t2/75EnWo4kZ5EHG15F3w6JVpD5RE7dafhqBjS9ckcvV91OhmfYz7JROOrCVqadiBdC v6mA== X-Gm-Message-State: ALoCoQk0Fm8uJrVDQRMbbmkPBwfVVO3Q8RuhGxR60EgdlSN1RWlJgkAVHuJDz+dFpegskg0wkOqm X-Received: by 10.180.188.13 with SMTP id fw13mr10784444wic.83.1411026315453; Thu, 18 Sep 2014 00:45:15 -0700 (PDT) Received: from [192.168.1.52] (g231233043.adsl.alicedsl.de. [92.231.233.43]) by mx.google.com with ESMTPSA id q13sm1932777wik.8.2014.09.18.00.45.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Sep 2014 00:45:14 -0700 (PDT) References:

Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <65F65883-3233-4777-A41A-5F45CE66D98C@thehoodiefirm.com> Cc: Robert Kowalski , Andy Wenk , "sebastianro@apache.org" , Klaus Trainer X-Mailer: iPhone Mail (11D257) From: Lena Reinhard Subject: Re: CouchDB Day Date: Thu, 18 Sep 2014 09:45:13 +0200 To: "marketing@couchdb.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org Hi Andy, good idea! Definitely +1 from my side. I'd then suggest we post this today and the News tomorrow (my computer broke= down and I'm having huge technical problems now which makes it impossible t= o ship them today, but I can get the News ready by tomorrow in any case). If you want me to proofread the post, just let me know. Also, if one of you g= ot any photos from the meetup, maybe you'll want to add them as well. Best Lena > On 17.09.2014, at 23:17, Andy Wenk wrote: >=20 > Hi Lena, >=20 > here is the recap of the CouchDB Meetup hamburg #3. I guess we could post > it as an own blog post and then link to it in the weekly news. What do you= > think? >=20 > :) >=20 > Thanks and Cheers >=20 > Andy >=20 > On 17 September 2014 22:30, Sebastian Rothbucher < > sebastianrothbucher@googlemail.com> wrote: >=20 >> Hi, >>=20 >> nehmt gern mein Recap unten wenn ihr m=C3=B6gt. >>=20 >> Bis dahin! >> Sebastian >>=20 >> P.S.: ich werde das n=C3=A4chste Meetup vermutlich nicht schaffen >>=20 >>=20 >> Recap Couch Meetup #3 >>=20 >>=20 >> We gathered at UbiLabs again =E2=80=93 on a Couch off course! >>=20 >>=20 >> Robert started out presenting an interactive tutorial to help get >> CouchDB started which will be on Github soon. It's no simulation =E2=80=93= it's >> getting hands dirty! And it's having a REAL Couch running and working at >> the end of it. >>=20 >>=20 >> While Robert started from the bottom, Meno approached Couch from the >> High Performance Computing perspective. Although Couch can certainly not >> compete with Hadoop, Cassandra and the likes in all aspects, there are go= od >> take-aways for Couch-based implementations and Couch itself like: >>=20 >> - >>=20 >> Unit of Work: atomic updates are possible to one document (only). So >> it is tempting to put a rather large graph (like a customer with all >> invoices) into one document which off course keeps growing until it is n= o >> more manageable. As it's not trivial to change this afterwards, one sho= uld >> consider Unit of Work carefully when designing an application. >> - >>=20 >> Adding VS updating of documents is another aspect: the more >> replication there is, the less likely it becomes to have no MVCC confli= ct. >> This does not apply for adding. And looking at systems like Cassandra t= hat >> are very good in adding (with transactional integrity), there is yet >> another architectural decision due. >> - >>=20 >> On the other hand, there is much room for improvement for retrieval of >> data. Some systems go as far as calculating the physical actions of har= d >> disks, the higher speed within a rack (compared to outside of it), etc >> - >>=20 >> This becomes even more useful as data grows really massively (i.e. >> there is massive sharding =E2=80=93 a feature which will certainly also= rock Couch >> with the BigCouch merge). >> - >>=20 >> Likewise: materializing the index (like Couch does) is per se a good >> thing to speed up retrieval (esp. as data keeps growing), but the effor= t to >> index keeps increasing anyway. This effort also implies wait times betw= een >> a Map-Reduce job is written and a result is there. >> - >>=20 >> The growth can reach an extent where a Map-Reduce on all data becomes >> impossible alltogether =E2=80=93 hence the new idea of just reading dat= a as it >> comes in, drawing summaries and throwing the base data away immediately= . >> This could overcome the notion that Big Data has a scaling limit ;-) >> - >>=20 >> The single point of failure (which for instance Hadoop-setups can >> have) is per se remedied with the Master-Master replication of Couch. >> - >>=20 >> The HTTP-based interface (while certainly being an advantage given the >> usual driver-mess) could lead to applications difficult to port away as= too >> many assumption about the underlying database are made. Although there a= re >> well-known examples of how to remedy this (like refactorings done for t= he >> NPM repository), taking action too late might result in unpleasantly lo= ng >> downtimes and high refactoring effort. >> - >>=20 >> When extending the HTTP communication with Couch and between Couches, >> HTTP will already offer many possibilities for negotiating the maximum o= f >> features both Couches understand. This can e.g. help in implementing re= sume >> of downloads during replication. >> - >>=20 >> As it's safe to NOT assume networks trustworthy, SSL in Couch in place >> is a plus >>=20 >>=20 >> So, it was a great evening again. >>=20 >>=20 >>=20 >>=20 >> 2014-09-17 17:05 GMT+02:00 Robert Kowalski : >>=20 >>> Hi Andy, >>>=20 >>> ich fands ganz witzig gestern, war aber noch immer viel zu fertig von de= r >>> JSConf.eu und nodeconf.eu - 8 Tage lang Konferenzmarathon. Meno war da, >>> und wir haben =C3=BCber alternative Datenbanken wie Cassandra und auch S= ysteme >>> wie Hadoop besprochen und was CouchDB fehlt. Cassandra fehlt leider auch= >>> ein paar Features mit den CouchDB auftrumpfen k=C3=B6nnte: Managen der R= acks die >>> nodes enthalten im Rechenzentrum. Danach sprachen wir =C3=BCber Security= : SSL, >>> Verschl=C3=BCsselung. Weiter gings dann mit m=C3=B6glichen Protokollimpl= ementierungen >>> f=C3=BCr ein neues Replikationsprotokoll f=C3=BCr CouchDB. >>>=20 >>> Da ich gerade einen initialen CouchDB-Workshopper baue (Annoncement auf >>> dev kommt bald) w=C3=BCrde ich mich freuen wenn jemand anderes die >>> Zusammenfassung macht. >>>=20 >>> Den CouchDB-Day habe ich kurz angesprochen, Klaus und Sebastian denken >>> auch dass es eine gute Idee ist. Ich kl=C3=A4re gerade mit Joan die Verw= endung >>> des Namen CouchDB / Apache CouchDB auf der Webseite zum Event. >>>=20 >>> Viele Gr=C3=BC=C3=9Fe, >>> Robert >>>=20 >>> Am 17. September 2014 11:20 schrieb Andy Wenk : >>>=20 >>> Hi Ihr, >>>>=20 >>>> wie war's gestern? Hat jemand Lust Lena eine kurze Zusammenfassung von >>>> gestern zu schicken? Und habt Ihr =C3=BCber den CouchDB Day gesprochen?= >>>>=20 >>>> Danke und Cheers >>>>=20 >>>> Andy >>>>=20 >>>>=20 >>>> 2014-09-16 8:55 GMT+02:00 Andy Wenk : >>>>=20 >>>>> Hallo Robert, >>>>>=20 >>>>> extremely awesome! Und dann sollten wir noch Jan und Noah einladen und= >>>>> wenn er mag auch Dave. Super gro=C3=9Fartige Idee. >>>>>=20 >>>>> Ich w=C3=BCrde gerne schreiben, lass uns das heute Abend mal anquatsch= en >>>>> aber leider hat sich ergeben, dass ich aus famili=C3=A4ren Gr=C3=BCnde= n heute Abend >>>>> doch nicht dabei sein kann. Sorry daf=C3=BCr. Ev. habt Ihr ja Lust das= schon mal >>>>> anzusprechen und dann lass uns das sehr bald angehen. >>>>>=20 >>>>> Ganz super geil! Das wird bestimmt cool. Danke Robert!!! >>>>>=20 >>>>> Cheers >>>>>=20 >>>>> Andy >>>>>=20 >>>>> 2014-09-15 21:53 GMT+02:00 Robert Kowalski : >>>>>=20 >>>>>> Hallo zusammen, >>>>>>=20 >>>>>> ich habe diese Idee von einem CouchDB-Day in Hamburg und w=C3=BCrde g= ern >>>>>> wissen was ihr davon denkt: >>>>>>=20 >>>>>> Leute k=C3=B6nnen vorbeikommen und mit uns an CouchDB arbeiten: das h= ei=C3=9Ft >>>>>> Code, Dokumentation, Translation, Artwork, Blogposts etc >>>>>>=20 >>>>>> Und Neulinge k=C3=B6nnen uns Fragen stellen, wie zum Beispiel das Apa= che >>>>>> Projekt funktioniert oder wo welcher Code ist und wie man ihn am best= en >>>>>> =C3=A4ndert. >>>>>>=20 >>>>>> Das ganze dann im Winter an einem Samstag von Mittags bis Abends. >>>>>>=20 >>>>>> Bis morgen, >>>>>> Robert >>>>>=20 >>>>>=20 >>>>>=20 >>>>> -- >>>>> Andy Wenk >>>>> Hamburg - Germany >>>>> RockIt! >>>>>=20 >>>>> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 >>>>>=20 >>>>> https://people.apache.org/keys/committer/andywenk.asc >>>>=20 >>>>=20 >>>>=20 >>>> -- >>>> Andy Wenk >>>> Hamburg - Germany >>>> RockIt! >>>>=20 >>>> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 >>>>=20 >>>> https://people.apache.org/keys/committer/andywenk.asc >=20 >=20 > --=20 > Andy Wenk > Hamburg - Germany > RockIt! >=20 > GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 >=20 > https://people.apache.org/keys/committer/andywenk.asc