-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Tale152
committed
Nov 20, 2022
1 parent
ff489d9
commit 9731826
Showing
2 changed files
with
10 additions
and
10 deletions.
There are no files selected for viewing
12 changes: 6 additions & 6 deletions
12
document/chapters/chapter_8/sections/1_expanding_the_prototype.tex
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,12 @@ | ||
\section{Expanding the prototype} | ||
The prototype seen in the previous chapter is just a fraction of the architecture theorized in this thesis work; this means that, with an incremental approach, further development for the actual software entities has to be made, starting from: | ||
The prototype seen in the previous chapter is just a fraction of the architecture theorized in this thesis work; this means that, with an \textbf{incremental approach}, further development for the actual software entities has to be made, starting from: | ||
\begin{itemize} | ||
\item iOS tested compatibility | ||
\item An easy-to-use GUI for the Interconnected Desktop Client, coupled with a guided installation process and automated start | ||
\item MapReduce algorithm implementation completion | ||
\item Making the Invoking Endpoint an actual dependency usable by other projects | ||
\item \textbf{iOS tested compatibility} | ||
\item \textbf{An easy-to-use GUI for the Interconnected Desktop Client, coupled with a guided installation process and automated start} | ||
\item \textbf{MapReduce's algorithm implementation completion} | ||
\item \textbf{Making the Invoking Endpoint an actual dependency usable by other projects} | ||
\end{itemize} | ||
|
||
Once these steps are completed, reaching a stability and maturity in the project development, the cloud side must be expanded with the final goal of obtaining the engineered cloud structure, starting from the creation of the dynamic system centered around the Grid Master Service. | ||
Once these steps are completed, reaching a stability and maturity in the project development, \textbf{the cloud side must be expanded} with the final goal of obtaining the engineered cloud structure, \textbf{starting from the creation of the dynamic system centered around the Grid Master Service}. | ||
|
||
After reaching a full working architecture, the next step in the evolution of the project comes from the implementation of new Grid Services. |
8 changes: 4 additions & 4 deletions
8
document/chapters/chapter_8/sections/2_implementing_new_services.tex
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,11 @@ | ||
\section{Implementing new Grid Services} | ||
Given the high focus on expandability that has driven this project, the possibilities for expanding the Grid's capabilities are endless. This section lists some ideas for future Grid Services. | ||
Given the high focus on expandability that has driven this project, \textbf{the possibilities for expanding the Grid's capabilities are endless}. This section lists \textbf{some ideas} for future Grid Services. | ||
|
||
\subsection{Simpler Services: Computation delegation} | ||
The MapReduce Service is a fantastic tool, but it is not ideal in every use case; MapReduce's limitations are well known in circumstances where the data pool to analyze is very limited in size and, thus, a simple computation delegation service is more indicated in those situations. By removing the recruitment process and the coordination between multiple entities, an Invoking Point can delegate a computation to a more powerful Node that will remotely execute the requested computation. | ||
The MapReduce Service is a fantastic tool, but it is not ideal in every use case; \textbf{MapReduce's limitations are well known in circumstances where the data pool to analyze is very limited in size} and, thus, a simple computation delegation service is more indicated in those situations. By removing the recruitment process and the coordination between multiple entities, \textbf{an Invoking Point can delegate a computation to a more powerful Node that will remotely execute the requested computation}. | ||
|
||
\subsection{More than computations: Storage sharing} | ||
Another wasted resource in users' Devices is storage space, frequently remaining unused; thus, another possibility for a Grid Service is to allow Contributors to share said storage space, implementing a distributed file retrieval system correlated with replication and fault tolerance mechanisms. | ||
Another wasted resource in users' Devices is storage space, frequently remaining unused; thus, another possibility for a Grid Service is to \textbf{allow Contributors to share said storage space}, implementing a \textbf{distributed file retrieval system correlated with replication and fault tolerance mechanisms}. | ||
|
||
\subsection{Reaching the physical world: Collective computing} | ||
Finally, one particular trait of mobile devices is the presence of multiple sensors. Given the participation of said devices to the Grid, some services can offer the possibility to access said sensors in order to obtain physical world data from the mobile devices of Contributors that allow such data retrieval. | ||
Finally, \textbf{one particular trait of mobile devices is the presence of multiple sensors}. Given the participation of said devices to the Grid, \textbf{some services can offer the possibility to access said sensors in order to obtain physical world data} coming from the mobile devices of Contributors that allow such data retrieval. |