Lorna Mitchell (01.Jul.2017 at 09:45, 45 min)
Talk at Dutch PHP Conference 2017 (English - US)
Come and meet CouchDB, the NoSQL store with magical powers. CouchDB is intended to be very fault-tolerant; it has excellent abilities to reconcile two databases that have been offline from one another for some time even with conflicting changes. This session will discuss the best use-cases for CouchDB and show you how you can use CouchDB from your own applications, including some of the shiny new features in the 2.0 release.
CouchDB uses MapReduce (written in JavaScript) for its views and offers some very powerful options for querying the data it stores. If you’re curious about alternative databases, especially for a large or growing application, then this session is for you.
Quicklink: https://legacy.joind.in/21165
Talk claims have been moved to the new Joind.in site.
Please login to the new site to claim your talk
Want to comment on this talk? Log in or create a new account or comment anonymously
03.Jul.2017 at 11:37 by Erik Roelofs (6 comments) via Web2 LIVE
This talk made me really excited to starting doing something with CouchDB. As someone who had heard of the fabled "no-sql" style of databases, but who never "got it", this talk really helped make it click. Lorna showed off these exciting pieces of software in an engaging way, very accessible to those new to the technology.
07.Jul.2017 at 15:26 by Arnout Boks (48 comments) via Web2 LIVE
Great talk, packed with loads of useful content. I liked the really clear explanations, good balance between slides and demo's and lively presentation style.
Know of an event happening? Let us know! We love to get the word out about events the community would be interested in and you can help us spread the word!
01.Jul.2017 at 10:40 by Jordan Kasper (73 comments)
Lorna is a very engaging speaker and provides a compelling use case. My biggest comment on this talk in particular is that it needs a later time slot! The content itself was good, but combining couch and pouch in one talk might be too much. For example, we didn't discuss authentication at all.