BASMATI - D2.3 Global Architecture Design

Carlini E., Coppola M., Dazzi P., De Lira V. M., Schwichtenberg A., Wacker R., Lechler C., Kim M., Lee D. altmann J., Haile N., Al-Athwari B. konstantinos Tserpes, John Violos, Vaggelis Psomakelis jamie Marshall young-Woo Jung, Dongjae Kang, Sunwook Kim, Ganis Zulfa Santoso enric Pages, Ana Juan Ferrer

Architecture  Integration 

The ultimate goal of the architecture work package of BASMATI is to ensure that all consortium members have a common vision of the global architecture of the system and that all developers are aware of the interfaces exported by any architecture component to others. This deliverable defines the architecture of the BASMATI platform. Overall, the objective of the BASMATI project is to design, implement and evaluate a dynamic and integrated brokerage platform targeting federated clouds that supports the dynamic needs of mobile applications and users. To this end, the BASMATI architecture provides a common ground to address key technological and research challenges in different research fields. These challenges mainly focus on three core aspects: (i) User, application and situation modelling and understanding to drive application placement; (ii) Runtime adaptivity and reconfiguration; (iii) Brokering and Offloading of application and services. The resulting architecture is divided into layers, which stem from several choices taken at design time. The first choice is the separation in the management of those services that natively run on the server side from those that run on a client device. The second choice is to separate the computational plane (how computation is organized, what are the functional dependencies from the services composing the application) from the data plane, in order to foster advanced computation and data orchestration techniques. The last, and probably the most important choice, is the definition of a specific application model (which we refer to as BEAM) that encompasses all the many views of the application within the platform. Finally, the architecture defined in this document has also been designed to support the requirements identified at the beginning of the project, from the use cases, in accordance with both the joint Korean and European use cases' needs. A final version of this document was created at M18.

Source: Project report, BASMATI, Deliverable D2.3, 2018