-
Notifications
You must be signed in to change notification settings - Fork 0
architecture
schleichardt edited this page Jan 14, 2013
·
11 revisions
We want to create a system that is simple as possible but provides high functional and load scalability. But scalability must be planned and integrated early in architecture.
It would be nice to have as few technologies, libraries and frameworks as possible.
- https://api.docear.org
- provides authentication
- source repository: https://github.com/Docear/HTW-Backend
- not reachable via internet
- i.e. hostname:8080
- provides working with mind maps
- source repository: https://github.com/Docear/HTW-Frontend
- https://my.docear.org ?
- provides HTML, CSS, JavaScript
- is proxy for other services
- not reachable via internet
- provides coordination
- provides workspaces and mind map files
- not reachable via internet
- provides build and testing every github push
- maybe responsible for one click deployments
- CAP theorem: it is impossible for a distributed computer system to simultaneously provide consistency, availability and partition tolerance (handling failures part of the system)
Architecture
- Architecture
- Continuous Integration
- Online View
- Frontend/API-Server
- Freeplane Remote
- Deployment
APIs
Research & Technologies
-
[Client layer - overview](wiki/Overview of used technologies for client layer)
Tutorials
Misc
Archive