It’s a good point but not for the marketing list unless you are talking just about producing blog posts or other materials to promote couchdb for that market?
I think to make couchdb more useful for iot would require some development work. Running couchdb on embedded devices is already a challenge and it’s only going to get harder in future. As a server side hub, the retention of a small amount of data after document deletion presents further problems. Briefly, this mailing list is for marketing only. If you wish to discuss project direction, post to the dev mailing list instead. Thanks. B. > On 6 Jul 2019, at 04:34, Chintan Mishra <chin...@rebhu.com> wrote: > >> On 21/06/19 4:51 PM, Chintan Mishra wrote: >> >> Dear team, >> >> I noticed this message on the Slack workspace by the user `@jan` >> >> https://couchdb.slack.com/archives/C49LEE7NW/p1560856033217500 >> >> Quoting the message in the link: >> >> this would require very little erlang and we can help with that >> part, what this project would need is someone who comes up with a >> compelling technical vision that goes beyond “works for me / solves >> my problems” and who is committed to maintain this going forward, >> find a team that helps, etc. >> >> After reading this, I realized there are a few things that we(CouchDB's team >> and Rebhu Computing's team) can do to help the CouchDB project right now. >> Here is a small list of those things: >> >> 1. *Organize a competition*for getting people to know about CouchDB. >> 2. *Make CouchDB more visible*. Unlike most other popular databases the >> online presence of CouchDB is not huge. Slack communication is not >> search indexed which makes it difficult to get new people to see all >> the things that are happening in the CouchDB world. > ---- >> 3. A *way forward for CouchDB is focusing on what it is best*at viz., >> being a database for _*C*__luster __*O*__f __*U*__nreliable >> __*C*__ommodity __*H*__ardware_. Being deploy-able at edge devices. >> Focusing on this will invite people building for IoTs towards >> CouchDB. And this will drive a whole new set of users/customers >> towards CouchDB and IBM's Cloudant project. We already use >> Cloudant's sync-android and CDTDatastore in our startup's(Rebhu >> Computing) product. >> > ---- > > I would like to draw attention to this point. I firmly believe that CouchDB > can benefit by targeting IoT device developers. IoT developers don't want to > worry about sending data from edge devices to server for processing. CouchDB > already has battle-tested replication strategy. Extending this for IoT devs > will drive the next age developers. CouchDB is already made for unreliable > systems and what is more unreliable than an IoT lying in the sea connected > with worldwide GSM/CDMA (2G) network. > >> Here are someways we, Rebhu Computing, can help right away: >> >> 1. We(Rebhu Computing) can organize a competition in India(Asia) where >> people build things using CouchDB. This can have *a theme to >> increase the number of participants*. And a jury can select the top >> 3 projects. The *winners get a T-Shirt* with CouchDB and startup's >> branding. And their project will be hosted by us(Rebhu Computing) >> for a year. >> 2. Migrate to Spectrum chat <https://spectrum.chat> and *make all of >> the CouchDB conversation search indexed*. No other DB community is >> actively doing this and it will improve CouchDB's ranking on >> DB-Engines website >> <https://db-engines.com/en/ranking/document+store>. I have >> personally wanted to do this for so long that I had already created >> a CouchDB group on Spectrum almost a year ago. >> 3. I would love to know the *viewpoint of the whole team* about the >> suggested way forward for CouchDB. >> >> >> -- >> Chintan Mishra >> Founder and CEO >> Rebhu Computing >>
