Platform Team/Sugar Network/Architecture: Difference between revisions

Line 7:

* The particular technical implementation is fully driven by real needs of deployments like [[Deployment_Team/Peru/Puno|one-teacher schools in Peru]] and should be as simple as possible;<br>[[Wikipedia:KISS_principle|Keep it simple, wise man!]];

* The system, from users point of view, should just work proving high-level services that cover the full collaboration circle that should exist within Sugar learning community;

* It is all about creating high-level services that use regular client-server interaction model with one addition, an optional need to make a synchronization between a distributed server and the main one, the Mothership; In other words, it is all time about having a chain of {{Code|Motherhip <-> [Distributed Server] <-> Client}} interactions.

* It is all about creating high-level services that use regular client-server interaction model with one addition, an optional need to make a synchronization between a distributed server and the main one, the Mothership; In other words, it is all time about having a chain of {{Code|Motherhip <-> [Distributed Server] <-> Client}} interactions; Because:

** Only on the Mothership level, there could be skilled people that can follow not trivial way to solve possible issues;

** Thus, either system should be smart enough to solve issues on its own or it should be as simple as possible delegating not trivial work to the Mothership; The 2nd option is taken;

== Overview ==

@@ Line 7: / Line 7: @@
 * The particular technical implementation is fully driven by real needs of deployments like [[Deployment_Team/Peru/Puno|one-teacher schools in Peru]] and should be as simple as possible;<br>[[Wikipedia:KISS_principle|Keep it simple, wise man!]];
 * The system, from users point of view, should just work proving high-level services that cover the full collaboration circle that should exist within Sugar learning community;
-* It is all about creating high-level services that use regular client-server interaction model with one addition, an optional need to make a synchronization between a distributed server and the main one, the Mothership; In other words, it is all time about having a chain of {{Code|Motherhip <-> [Distributed Server] <-> Client}} interactions.
+* It is all about creating high-level services that use regular client-server interaction model with one addition, an optional need to make a synchronization between a distributed server and the main one, the Mothership; In other words, it is all time about having a chain of {{Code|Motherhip <-> [Distributed Server] <-> Client}} interactions; Because:
+** Only on the Mothership level, there could be skilled people that can follow not trivial way to solve possible issues;
+** Thus, either system should be smart enough to solve issues on its own or it should be as simple as possible delegating not trivial work to the Mothership; The 2nd option is taken;
 == Overview ==