-
Notifications
You must be signed in to change notification settings - Fork 342
Server architecture
Vincent den Boer edited this page Apr 9, 2018
·
1 revision
NOTE: These are some high-level notes about the server architecture shared between Memex Cloud and the local server to be organized further (TODO: think of cool name for local server) NOTE: Where possible, try to organize this Wiki so it's easily re-used for white-paper
Components needing software outside the browser:
- Backup
- Sync between devices
- Server for thin client like mobile needing to search history index
- Sharing (although DAT may get integrated into browsers. TODO: Find and link more info about this.)
Sharing includes sharing of:
- Select parts of history
- Lists
- Highlights / comments
- Article ratings
The following features are part of the premium Memex Cloud:
- Easy to use backup
- Sync between devices (especially useful for lists)
- Mobile client
- Asynchronous sharing
The following features are available for free:
- (Manual?) backup to Google Drive (and Dropbox?)
- Synchronous sharing after installing the local server
High-level goals of architecture:
- Accommodate gradual approach to decentralization in software architecture
- Cost-efficient to run on centralized infrastructure
- Fool-proof deployment procedures through DevOps
- Design in modular fashion with testability in mind through Test Driven Development