For the week ending 9 April 2021

A Resonance Calendar

Sources that have caught my attention and from which I’ve taken away something (that feels) important. In other words, something that resonates.
A few links and with an excerpt from each.

The InterPlanetary File System is a protocol and peer-to-peer network for storing and sharing data in a distributed file system. IPFS uses content-addressing to uniquely identify each file in a global namespace connecting all computing devices. [InterPlanetary File System — Wikipedia]

Pinata is the simplest way to upload and manage files on IPFS. Our friendly user interface combined with our IPFS API makes Pinata the easiest IPFS pinning service for platforms, creators, and collectors.

Several significantly different attempts have been undertaken to visualize the complex and opaque cloud computing ecosystem by a descriptive model. Recently, scholars have developed a new role-based cloud ecosystem model (Passau Cloud Computing Ecosystem Model (PaCE model)) based on a systematic analysis and synthesis of the previous models. … (A) cross-sectional analysis is conducted, in which 758 organizations are manually analysed and matched with the model’s current roles. …. Overall, the revised model creates, compared to the common rather technically orientated market overviews by market research institutes, a detailed categorization schema helping to understand and investigate the organizations belonging to the cloud ecosystem.

Cloud Computing has developed rapidly over the last ten years with worldwide spending on public and private cloud hosting passing the $32bn. mark this year, and savings to businesses using the cloud are typically stated as better than 30% due to the cloud’s ability to better take advantage of economies of scale. Yet, in actuality, in commercial data centres the utilization of resources still remain low. In this paper we introduce a new approach from CloudWave which uses user-defined performance goals as well as monitoring across the Cloud ecosystem as a means for guiding runtime adaptation of both the cloud infrastructure and the hosted service to improve overall performance.

In this paper, we introduce a baseline performance evaluation in order to identify the fallacies and pitfalls of combining multiple cloud systems and mobile edge computing (MEC) into a unified MEC-multi-cloud platform. For this purpose, we analyze the basic, application-independent performance metrics of average round-trip time (RTT) and average application payload throughput in a setup consisting of two private and one public cloud systems. This baseline performance analysis confirms the feasibility of MEC-multi-cloud and provides guidelines for designing an autonomic resource provisioning solution in terms of an extension proposed to our existing Melodic middleware platform for multi-cloud applications.

The introduction of a centralized component, the Cloud Governance, is necessary in order to enable the development of complex cloud ecosystems. This centralized component is extending, complementing, completing and integrating core features from the PaaS layer, like monitoring, provisioning, negotiation, and others, and integrate features of various Cloud management solutions.

The purpose of this paper is to provide a brief overview of cloud computing technologies, particularly with respect to multi-cloud networks. First, the basics of cloud computing concepts are discussed. Next we outline some challenges facing cloud computing, and discuss how multi-cloud systems including multi-clouds, hybrid clouds, federated clouds, and cross-clouds may be used to deal with some of these issues. Finally, multi-cloud systems may also be used in conjunction with new developing technologies such as Big Data and Machine Learning, leading to exciting innovations.

(G)iven the plethora of distinct services involved in the Cloud ecosystem and the varied attack surfaces entailed in the Cloud-specific architectures, performing threat analysis for the Cloud is a challenging task. Consequently, contemporary Cloud threat analysis approaches, typically using relational security models (e.g., attack graphs, trees…), primarily focus on specific services/layers of the Cloud. (T)hese schemes often fail to include the variants of the identified vulnerabilities in their analysis.

In this article, I want to explain:
* what is the Document Object Model (DOM),
* what is Shadow DOM,
* what is Virtual DOM,
* what is the difference between Shadow DOM and Virtual DOM

I will also try to tell you about the differences between them and what advantages and disadvantages each of them brings.

Silicon Valley irregular, CEO of Telematica, Inc. and Executive Chairman of Provenant Data, Inc.