So you do have something ready for large scale or at least redundancy. My main concern is about "if my server crash ... how my users will sync". I may have overestimated for the 100k users, but the 10k is real for the project we are working on, and with this kind of clients I must have something to be sure the service won't be offline.
About 1.5 instead of 1.1, if Nick is able to provide me an APK with this custom url support (I don't have the tools/knowledge to compile the apk myself) i'll work on the 1.5 after being ready with 1.1. Why ? Because of FXA. As it's a new "feature", I'm afraid to lose a lot of time (i must deliver a PoC for the 17th jully) because the documentation is very "young". The fact is, I learn to work with a lot of technologies I'm not use to (WSGI, apache, PostgreSQL, ...). im must focus on something that work in few time and provide a documentation which cover : Sync architecture, protocols, network requirement (for loadbalancer), PoC sept-by-step, ... Past this date I'll be able to work on the evolution of the service with 1.5 Our main concern for future is support of SSO. As Firefox will be a part of a larger project, we require that most of our "integrated solutions" to be SSO-compliant. Do you think it's possible with Sync 1.5 atm ? Robin Aleman Apprentice engineer - Software integration Customer Integration & Support EQUANT France - Sophia Antipolis +00 33 4 92 96 64 48 [email protected] -----Original Message----- From: Ryan Kelly [mailto:[email protected]] Sent: Thursday, July 03, 2014 06:56 To: [email protected]; ALEMAN Robin SCE/ID ITS Subject: Re: Hello! On 3/07/2014 1:45 AM, [email protected] wrote: > ATM I have a postgreSQL database working and an Apache under > construction (if I may). I'm looking for information about sync > architecture and how to implement some fun things like : SSO > (Kerberos), load balancing, backup, ... anything usefull for a large > scale of user (10k to 100k). So we do have a tiny bit of Secret Scalability Sauce that's not part of the default self-hosted sync setup, because it's kinda fiddly and is not required until you start pushing very large numbers of users. Basically, we run multiple storage nodes and have each user account assigned to sync to a specific node. If you're connected to the Mozilla-hosted sync system, go into "about:config" in Firefox and search for "clusterURL". You'll see something like: clusterURL: https://sync-60-us-west-2.sync.services.mozilla.com/1.5/3597148/ That's my "sync node". This is a very simple scheme for splitting the load across multiple machines. For Sync1.1 this is part of the authentication API, and the server that's responsible for it is called the "node assignment server": http://hg.mozilla.org/services/server-node-assignment For Sync1.5 the same job is done by the new authentication server, called the "tokenserver": http://docs.services.mozilla.com/token/index.html https://github.com/mozilla-services/tokenserver > For now I'm working on Sync 1.1 due to Fennec incompatibility with > Sync > 1.5 custom server. Given Nick's reply about the imminent availability of this in Fennec, are you interested in switching over to Sync1.5? I'll avoid overloading you with further details of either system for now. Cheers, Ryan _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
