Privacy/Reviews/Firefox Home: Difference between revisions

Privacy/Reviews/Firefox Home (view source)

Revision as of 21:10, 27 April 2011

1,219 bytes added , 27 April 2011

→‎Home Server

St3fan

Confirmed users

971

edits

@@ Line 120: / Line 120: @@
 |}
-=== Home Server  ===
+=== Home Web Servers ===
-The 'Home Server' consists of three separate entities:
+We will have stateless web servers that run the Home web application. These are standard web servers running Apache or NGINX to serve the Home web application.
+These servers will likely be load balanced by Zeus.
+These servers are supposed to be stateless so no data will stored on these servers. However, they might have sensitive configuration settings stored on them. For example things like web service keys or tokens that we need to connect to third party services. These are not user specific but instead are for the Home application.
+(These external services have not been identified yet, but think about services like bit.ly.)
-* Web Servers
+The tables below simply summarize the data encountered by this component.
-* Database Servers
-* Memcache Servers
-These will all be hosted on separate machines (or initially, VMs) and such will also be configured with very strict access permissions.
+'''Stored Data:'''
-==== Web Servers ====
+{| class="wikitable"
+|-
+! What
+! Where
+|-
+| data type
+| where stored
+|}
-We will have stateless web servers that run the Home web application. These are standard web servers running Apache or NGINX to serve the Home web application.
+'''Communication with Crypto Proxy'''
-These servers will likely be load balanced by Zeus.
+{| class="wikitable"
+|-
+! Direction
+! Message
+! Data
+! Notes
+|-
+| ''In:''
+| message 1
+| types of data received from component Y with the message
+|
+|-
+| ''Out:''
+| message 2
+| types of data sent to component Y with the message
+|
+|}
-These servers are supposed to be stateless so no data will stored on these servers. However, they might have sensitive configuration settings stored on them. For example things like web service keys or tokens that we need to connect to third party services. These are not user specific but instead are for the Home application.
+'''Communication with [[Services/Sync|Sync Server]]'''
-(These external services have not been identified yet, but think about services like bit.ly.)
+{| class="wikitable"
+|-
+! Direction
+! Message
+! Data
+! Notes
+|-
+| ''In:''
+| message 1
+| types of data received from component Y with the message
+|
+|-
+| ''Out:''
+| message 2
+| types of data sent to component Y with the message
+|
+|}
-==== Database Servers ====
+=== Database Servers ===
 User data will sharded over a number of database servers. We will use a simple hashing mechanism so that we can determine where a user's data lives based on for example their username.
@@ Line 152: / Line 195: @@
 One thing we will probably do is run some queries offline. For example we can periodically 'calculate' a list of your top sites and store that in a database table too.
-==== Memcache Servers ====
+The tables below simply summarize the data encountered by this component.
+'''Stored Data:'''
+{| class="wikitable"
+|-
+! What
+! Where
+|-
+| data type
+| where stored
+|}
+'''Communication with Crypto Proxy'''
+{| class="wikitable"
+|-
+! Direction
+! Message
+! Data
+! Notes
+|-
+| ''In:''
+| message 1
+| types of data received from component Y with the message
+|
+|-
+| ''Out:''
+| message 2
+| types of data sent to component Y with the message
+|
+|}
+'''Communication with [[Services/Sync|Sync Server]]'''
+{| class="wikitable"
+|-
+! Direction
+! Message
+! Data
+! Notes
+|-
+| ''In:''
+| message 1
+| types of data received from component Y with the message
+|
+|-
+| ''Out:''
+| message 2
+| types of data sent to component Y with the message
+|
+|}
+=== Memcache Servers ===
 The tables below simply summarize the data encountered by this component.