Fig 3 - uploaded by Nane Kratzke
Content may be subject to copyright.
The conceptual data model: The relation to descriptive cluster definition formats is shown as well (please compare with Appendices A, B, C, D).
Source publication
Cloud-native applications are often designed for only one specific cloud infrastructure or platform. The effort to port such kind of applications into a different cloud is usually a laborious one time exercise. Modern Cloud-native application architecture approaches make use of popular elastic container platforms (Apache Mesos, Kubernetes, Docker S...
Contexts in source publication
Context 1
... conceptual model shown in Figure 3 is used tp describe the deployment of elastic platforms in multi-cloud scenarios and considers arbitrary IaaS cloud service providers [18]. Public cloud service providers organize their IaaS services using mainly two approaches: project-and region-based service delivery. ...
Context 2
... the approaches are given and multi-cloud solutions must prepared that both approaches occur in parallel. The conceptual model integrates both approaches introducing a concept called District (see Figure 3). A District can be understood as a user defined "datacenter" which is pro- vided by a specific cloud service provider (following the project-or region-based approach). ...
Context 3
... proposed prototype can work with arbi- trary roles and rolenames. Role-specifics can be considered by Platform drivers (see Figure 3) in their install, join and leave cluster hooks (see Figure 4). A typical Deployment can be expressed using this JSON snippet. ...
Context 4
... handling of infrastructure and platform specifics is done using an extendable driver concept (see Figure 3). The classes Platform and Infrastructure form two extension points to provide support for IaaS infrastructures like AWS, GCE, Azure, DigitalOcean, RackSpace, ..., and for elastic container platforms Table 4 shows how this has been applied for di↵erent IaaS drivers. ...
Similar publications
A data scientific process (e.g., Obtain, Scrub, Explore, Model, and iNterpret (OSEMN)) usually consists of different steps and can be understood as an umbrella for the combination of different most modern techniques and tools for the extraction of information and knowledge. When developing a suitable IT infrastructure for a self-service platform in...
