Management and Service-aware Networking Architectures (MANA) for Future Internet Position Paper: System Functions, Capabilities and Requirements

Future Internet (FI) research and development threads have recently been gaining momentum all over the world and as such the international race to create a new generation Internet is in full swing: GENI, Asia Future Internet, Future Internet Forum Korea, European Union Future Internet Assembly (FIA). This is a position paper identifying the research orientation with a time horizon of 10 years, together with the key challenges for the capabilities in the Management and Service-aware Networking Architectures (MANA) part of the Future Internet (FI) allowing for parallel and federated Internet(s)

Designing community care systems with AUML

This paper describes an approach to developing an appropriate agent environment appropriate for use in community care applications. Key to its success is that software designers collaborate with environment builders to provide the levels of cooperation and support required within an integrated agent–oriented community system. Agent-oriented Unified Modeling Language (AUML) is a practical approach to the analysis, design, implementation and management of such an agent-based system, whilst providing the power and expressiveness necessary to support the specification, design and organization of a health care service. The background of an agent-based community care application to support the elderly is described. Our approach to building agent–oriented software development solutions emphasizes the importance of AUML as a fundamental initial step in producing more general agent–based architectures. This approach aims to present an effective methodology for an agent software development process using a service oriented approach, by addressing the agent decomposition, abstraction, and organization characteristics, whilst reducing its complexity by exploiting AUML’s productivity potential. </p

Design and implementation of a federated health record server

This paper describes the practical implementation of a federated health record serverbased on a generic and comprehensive public domain architecture and deployed in alive clinical setting.The authors, working at the Centre for Health Informatics and MultiprofessionalEducation (University College London), have built up over a decade of experiencewithin Europe on the requirements and information models that are needed to underpincomprehensive multi-professional electronic health records. This work has involvedcollaboration with a wide range of healthcare and informatics organisations and partnersin the healthcare computing industry across Europe though the EU Health Telematicsprojects GEHR, Synapses, EHCR-SupA, SynEx and Medicate. The resultingarchitecture models have influenced recent European standards in this area, such asCEN TC/251 ENV 13606. UCL has now designed and built a federated health recordserver based on these models which is now running in the Department ofCardiovascular Medicine at the Whittington Hospital in north London. A new EC FifthFramework project, 6WINIT, is enabling new and innovative IPv6 and wirelesstechnology solutions to be added to this work.The north London clinical demonstrator site has provided the solid basis from which toestablish "proof of concept" verification of the design approach, and a valuableopportunity to install, test and evaluate the results of the component engineeringundertaken during the EC funded projects

Two ways to Grid: the contribution of Open Grid Services Architecture (OGSA) mechanisms to service-centric and resource-centric lifecycles

Service Oriented Architectures (SOAs) support service lifecycle tasks, including Development, Deployment, Discovery and Use. We observe that there are two disparate ways to use Grid SOAs such as the Open Grid Services Architecture (OGSA) as exemplified in the Globus Toolkit (GT3/4). One is a traditional enterprise SOA use where end-user services are developed, deployed and resourced behind firewalls, for use by external consumers: a service-centric (or ‘first-order’) approach. The other supports end-user development, deployment, and resourcing of applications across organizations via the use of execution and resource management services: A Resource-centric (or ‘second-order’) approach. We analyze and compare the two approaches using a combination of empirical experiments and an architectural evaluation methodology (scenario, mechanism, and quality attributes) to reveal common and distinct strengths and weaknesses. The impact of potential improvements (which are likely to be manifested by GT4) is estimated, and opportunities for alternative architectures and technologies explored. We conclude by investigating if the two approaches can be converged or combined, and if they are compatible on shared resources

Hybrid clouds for data-Intensive, 5G-Enabled IoT applications: an overview, key issues and relevant architecture

Hybrid cloud multi-access edge computing (MEC) deployments have been proposed as efficient means to support Internet of Things (IoT) applications, relying on a plethora of nodes and data. In this paper, an overview on the area of hybrid clouds considering relevant research areas is given, providing technologies and mechanisms for the formation of such MEC deployments, as well as emphasizing several key issues that should be tackled by novel approaches, especially under the 5G paradigm. Furthermore, a decentralized hybrid cloud MEC architecture, resulting in a Platform-as-a-Service (PaaS) is proposed and its main building blocks and layers are thoroughly described. Aiming to offer a broad perspective on the business potential of such a platform, the stakeholder ecosystem is also analyzed. Finally, two use cases in the context of smart cities and mobile health are presented, aimed at showing how the proposed PaaS enables the development of respective IoT applications.Peer ReviewedPostprint (published version

Data Mesh: a Systematic Gray Literature Review

Data mesh is an emerging domain-driven decentralized data architecture that aims to minimize or avoid operational bottlenecks associated with centralized, monolithic data architectures in enterprises. The topic has picked the practitioners' interest, and there is considerable gray literature on it. At the same time, we observe a lack of academic attempts at defining and building upon the concept. Hence, in this article, we aim to start from the foundations and characterize the data mesh architecture regarding its design principles, architectural components, capabilities, and organizational roles. We systematically collected, analyzed, and synthesized 114 industrial gray literature articles. The review provides insights into practitioners' perspectives on the four key principles of data mesh: data as a product, domain ownership of data, self-serve data platform, and federated computational governance. Moreover, due to the comparability of data mesh and SOA (service-oriented architecture), we mapped the findings from the gray literature into the reference architectures from the SOA academic literature to create the reference architectures for describing three key dimensions of data mesh: organization of capabilities and roles, development, and runtime. Finally, we discuss open research issues in data mesh, partially based on the findings from the gray literature