Hi Jens,

Thanks very much for the feedback.

Today I created my first AWS account just to see if I could get Sync 
Gateway and Couchbase Server 4 community editions running. There's a lot to 
learn it seems.

I'll work on the documentID UUID issue and I have a question about that 
which I'll post in a separate thread.

I think maybe if I can offer my customers various options that would be 
ideal. So I'm thinking 3 ways to sync:

   1. Peer to peer.
   2. Shared service via my AWS instance.
   3. User provides their own CouchDB compatible server (Cloudant or 
   Couchbase).
   
I guess the problem will be managing authentication for any of those 
services.

I'll have to scour the documentation and tutorial videos to find some 
information on that. Or see if I can hire someone to help me set them up. I 
used to do server app development, but that was with WebObjects running on 
our own OS X Xserves. Haven't really done anything server side in about 5 
years.

Thanks,

Brendan

On Thursday, October 29, 2015 at 4:56:13 PM UTC-6, Jens Alfke wrote:
>
>
> On Oct 29, 2015, at 11:11 AM, Brendan Duddridge <[email protected] 
> <javascript:>> wrote:
>
> Hi, 
>
> I'm looking for a Couchbase hosting service to provide Couchbase Lite 
> replication services for my (non-enterprise) Mac and iOS apps. 
>
>
> I’m not aware of any hosted services other than Cloudant. I’ve heard talk 
> of companies setting up Couchbase Server / Sync Gateway hosting services, 
> but I haven’t hard of any that are running yet. (But don’t take this as a 
> definitive ‘no’.)
>
> One halfway option is to run your own virtual server using a service like 
> AWS or Heroku. Couchbase has pre-configured images you can install to 
> instantly set up a system with Couchbase Server and Sync Gateway.
>
>
>    1. Security. I don't want to have access to any user's data. All 
>    communication with server must be secure. Storage of user data must be 
>    secure.
>    
> Those are different things. Secure communications is just SSL, of course. 
> Secure storage could just mean that the provider is doing its job enforcing 
> access control. But for *you* to not have access to user data implies 
> that the data has to be encrypted, with the user holding the decryption 
> key. That’s not something we support yet, although there are hooks in the 
> replication API for doing it (there’s a callback you can register to 
> transform a doc’s contents when it’s pushed or pulled.)
>
>
>    1. Each user must have their own databases. I don't want documents 
>    from one user intermixed with documents of another user. One reason is for 
>    security, another is that different users can possibly have documents with 
>    the same documentID. I think having separate databases solves this 
> problem. 
>    I'm not sure if Couchbase Server's "channels" feature allows for this.
>
> Database-per-user is feasible as long as users don’t share documents. If 
> they do, then those databases all need to replicate with each other on the 
> server side, which is difficult to configure and runs into scaling 
> problems. (This was the very issue that led Chris Anderson to come up with 
> the idea of channels.)
>
> With Sync Gateway there would only be a single database, but channels 
> govern user access to data. You do need to ensure that different users’ 
> docs don’t have the same docIDs — either use UUIDs only, or put the userID 
> into the docID.
>
>
>    1. A nice to have would be direct client billing. I would prefer if my 
>    customers had to sign-up for an account and pay for the service themselves 
>    rather than me having to pay on their behalf.
>
> If there’s really no sharing between user data, you could even have every 
> user sign up for their own Cloudant account. Then you don’t have to deal 
> with accounts or billing at all, and you definitely don’t have access to 
> their data :)
>
> —Jens
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/9e2eb6af-55ce-4234-b0b3-2ceeb2101304%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to