System Architecture.html - pabloviquez/docutest GitHub Wiki
Starkey Foundation - Starkey Video : System Architecture
This page last changed on Apr 21, 2014 by pablo.viquez.
Main Navigation
Home - Discovery & Architectur- e
Starkey Architecture Navigation
Home - Discovery & Architectur- e
[Non-Function- al Requirement- s](/display/STARKEYVID/Non- Functional+Requirements)
System Architecture
There are several ways to construct the system architecture. We're proposing a less coupled system and adding a new layer for cache.
Standard Setup
This is the default Expression Engine setup, all templates and coding lives within the Expression Engine System.
Proposed System
Comparison
Standard Setup
Benefits Cons
Everything on one place
High coupling with the CMS
For developers it's simpler the setup
Administration area if not change, its easier to guess for outside people
Creates greater experience on the CMS since everything must be done there
Migrations to another system are more complicated
Proposed Setup
Benefits Cons
Loose coupling between components
Requires gathering knowledge of the system
API being developed can serve for future implementations
Setup requires administration of extra components
Another caching layer can be put in place to reduce impact in database
Server side developers have a bigger learning curve
CMS migrations are easier, since all communications are being done using a REST interface
Extra implementations can be put in place even if the CMS does not support it
Client side work does not require to know anything about the CMS
Client side can implement any type of architecture without worrying about breaking CMS functionality
In This Page
- System Architecture
- Standard Setup
- Proposed System
- Comparison
- Standard Setup
- Proposed Setup
Site Map
Attachments:
Architecture_Standard.png (image/png)
Architecture_Proposed.png (image/png)
Architecture_Proposed.png (image/png)
Architecture_Standard.png (image/png)
Document generated by Confluence on Sep 16, 2014 14:12