On Oct 29, 2015, at 11:11 AM, Brendan Duddridge <brend...@gmail.com<mailto:brend...@gmail.com>> 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 mobile-couchbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/4BF26BA8-5BC5-4EC1-AFFF-0FFCAEBC17A0%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
