Confirmed users
230
edits
Gaia/Architecture Proposal: Difference between revisions
Jump to navigation
Jump to search
→Back-End as Services
| Line 364: | Line 364: | ||
= Back-End as Services = | = Back-End as Services = | ||
The hard split between the front-end and the back-end will let us explore alternative models, where both can runs onto | The hard split between the front-end and the back-end will let us explore alternative models, where both can runs onto different processes, using the same bridge mediator code. | ||
'' | |||
Note: A new WebAPI is needed to allow cross-origin communication safely and efficiently, and in order to open those Services to third-party app. In the meantime this can be prototype for default apps only, in order to see how it behaves.'' | |||
== One front-end / One Service == | == One front-end / One Service == | ||
| Line 376: | Line 379: | ||
== Multipe front-ends / Multiple services == | == Multipe front-ends / Multiple services == | ||
Since the back-end is the one responsible to manage applications data, the same set of data can be shared across multiple front-ends. | Since the back-end is the one responsible to manage applications data, the same set of data can be shared across multiple front-ends. | ||
As a result it can be multiple application, displaying user datas in various ways, running at the same time. | |||
[[File:Gaia Architecture Proposal MultiApp MultiProcess MultiThread.png|600px]] | [[File:Gaia Architecture Proposal MultiApp MultiProcess MultiThread.png|600px]] | ||