Confirmed users
927
edits
Apps/ServerArchitecture: Difference between revisions
→Sauropod Node.JS server ?
RyanTilder (talk | contribs) |
Tarek.ziade (talk | contribs) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
http://ziade.org/appsync.png | http://ziade.org/appsync.png | ||
= Overview = | |||
* The appsync server provides | |||
** appsync APIs | |||
** the static myapps website | |||
** a MySQL database that mirrors all writes | |||
* The sauropod server is a Node.js server | |||
** keeps sessions in memory (DB tokens) | |||
** proxies the calls to the HBAse server | |||
* The HBase cluster manage the data | |||
= appsync/myapps = | = appsync/myapps = | ||
| Line 31: | Line 41: | ||
* status - DEPLOYED | * status - DEPLOYED | ||
= Sauropod Node.JS server | = Sauropod Node.JS server = | ||
* Points of contact | * Points of contact | ||
| Line 40: | Line 50: | ||
* stack | * stack | ||
** CentOS6 | ** CentOS6 | ||
** | ** node.js 0.6.3 from mozilla-services package repository | ||
* status - | ** direct checkout from github | ||
* CI / CD - | * status - Hackishly deployed | ||
* CI / CD - not yet | |||
= Sauropod HBase stack = | = Sauropod HBase stack = | ||