Skip to main navigation Skip to search Skip to main content

Infrastructure-as-Code for Data-Intensive Architectures: A Model-Driven Development Approach

  • Matej Artac
  • , Tadej Borovsak
  • , Elisabetta Di Nitto
  • , Michele Guerriero
  • , Diego Perez-Palacin
  • , Damian Andrew Tamburri

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

Abstract

As part of the DevOps tactics, Infrastructure-as-Code (IaC) provides the ability to create, configure, and manage complex infrastructures by means of executable code. Writing IaC, however, is not an easy task, since it requires blending different infrastructure programming languages and abstractions, each specialized on a particular aspect of infrastructure creation, configuration, and management. Moreover, the more the architectures become large and complex (e.g. Data-Intensive or Microservice-based architectures), the more dire the need of IaC becomes. The goal of this paper is to exploit Model-Driven Engineering (MDE) to create language-agnostic models that are then automatically transformed into IaC. We focus on the domain of Data-Intensive Applications as these typically exploit complex infrastructures which demand sophisticated and fine-grained configuration and re-configuration - we show that, through our approach, called DICER, it is possible to create complex IaC with significant amounts of time savings, both in IaC design as well as deployment and re-deployment times.

Original languageEnglish
Title of host publication2018 IEEE International Conference on Software Architecture (ICSA)
PublisherInstitute of Electrical and Electronics Engineers
Pages156-165
Number of pages10
ISBN (Electronic)978-1-5386-6398-1
DOIs
Publication statusPublished - 20 Jul 2018
Externally publishedYes

Keywords

  • Big Data
  • Cloud
  • DevOps
  • Infrastructure-as-Code
  • Model-Driven Engineering
  • TOSCA

Fingerprint

Dive into the research topics of 'Infrastructure-as-Code for Data-Intensive Architectures: A Model-Driven Development Approach'. Together they form a unique fingerprint.

Cite this