Infrastructure as code tools for modern SaaS

PaaS deployment

Infrastructure as Code technology solutions and tools for an optimized SaaS architecture

Describes the key principles between infrastructure code, model and deployment in an automated environment.

discover more

our aproach

Find out how a SaaS architecture model leads to automated Infrastructure as Code

Layerscape principle

IaC - model - simulation

discover more

dev and IaC blog

Interesting articles about infrastructure as code and development.

The articles are written by developers for developers and delve deep into the subject matter.

discover more

Motivation

:: Infrastructure as Model and Code - tools

Our ideas to rethink the design process of SaaS architecture is based on modeling the solution at an early stage, i.e. about as early as the business modeling phase. In contrast to all software architecture programs available on the market, the added value lies in the fact that it is far more than just a drawing. Moreover, you can transfer the abstract model to the real available resources of the three major cloud providers. However, it is also possible to translate between the PaaS systems and hybrid solutions are also conceivable. In addition to the deployment code created, you can also automate the reverse engineering of a model from the existing code.

:: our vision

We want to use our expertise to develop infrastructure-as-code tools that help all companies secure their digital business model in a cost-efficient and scalable way. Moreover, we are doing everything we can to ensure that our solution becomes an elementary part of the tool chain for the automated infrastructure deployment of modern SaaS solutions.

Infrastructure as Code toolset - Layerscape principle

The structure follows the layer principle, so that the view of the solution always corresponds to the role of the editor. The modeling layer is usually the starting point for designing the solution. Depending on preference, this can be done in abstract form or with the resources of a preselected cloud provider. Each resource is mapped as a block, has functionally identical platform twins (Azure, AWS, Google Cloud) and contains the underlying function, the cost and scaling model as well as the infrastructure code for the system.

New ideas for automated Infrastructure as Code tools

Our approach allows the automatic generation of infrastructure code from the SaaS model, which you can also edit manually. This distinguishes our Infrastructure as Code Tools from Terraform or platform-specific solutions such as Azure Bicep or AWS CloudFormation. All layers rely on the same base model, ensuring that changes at the code level transfer back into the model. Another particular strength of our SaaS tool is its support and management of various deployment stages, which are unavoidable during development. This includes at least one development and test stage in addition to the productive system. The simulation view enables you to carry out simulations for individual features or the entire solution, providing the following insights:

How high are the operating costs?
Does the solution scale as desired?
How to configure the platform resources?

Simulation

The technology solution is shown with which a SaaS architecture model can be simulated in terms of costs and scaling due to our tools and ideas.

The chart shows the results of our technology solution for SaaS operating costs estimation. It enables our clients to optimize SaaS architecture.

The basic principle of cost and scaling simulation is quite simple to understand. The SaaS architecture example of a central heating system described on the home-site is used for this purpose. Furthermore, the model is enriched with iClients. These are digital twins of a component or a person that trigger data processing. Moreover, you configure the iClients with regard to their mode of operation, i.e., time-controlled, statistical distributions, randomized, etc., to introduce a load into the model that corresponds to your application. Consequently, our SaaS tools numerically determine statements about resource configuration, scalability, and expected costs as a function of time.

Welcome to tech-blog preview!

We are constantly writing new posts and interesting articles on topics such as cloud infrastructure, infrastructure as code, tools, SaaS architecture and best practices. Specifically, we address developers, solution architects and decision-makers in digitalization projects. Furthermore, we would like to provide you with a toolset of best practice principles for Software as a Service to further strengthen your success story.

SHOW ALL POSTS >>

The articles come from our professional experience rather than being constructed. We are also always interested in new exciting topics, case studies and guest articles. If you have a topic or problem that fits into this context, we invite you to get in touch with us. Perhaps we can give you some positive input free of charge!

Thank you for your interest!

A colorful biceps is displayed with a cloud floating above it. In between is an Azure Blob Storage Account icon. The image is synonymous for Infrastructure as Code created by using Azure Bicep to deploy a Blob Storage Account.

Azure Storage Accounts with Bicep – a tutorial

This tutorial covers concepts and best practice principles for creating Azure storage accounts with Bicep. In this blog article series, which consists of 5 parts, the basics of the language are explained and code examples with storage accounts are given. For those who are just starting out and are not yet familiar with Azure bicep, I recommend starting with the first part “bicep basics” of the tutorial. This is followed by articles on functions, IoT Hub and Cosmos DB using a sample environment that can be deployed fully automatically at the end

Michael February 10, 2025

It's synonymous for Infrastructure as Code created by using Azure Bicep as tutorial. A colorful biceps is displayed with a cloud floating above it. In between is an Azure bicep icon.

Bicep tutorial – Azure IaC basics

Bicep is a language and toolset used for defining infrastructure as code for azure. It can be used to describe ressources in sufficient detail and to combine those Descriptions to the description of a whole environment. It abstracts some of the complexity of dealing with Azure Ressource Manager (ARM) Templates, that are basically just very large json files Bicep is very easy to learn and offers good tooling. In this series of posts I want have a look at some of it’s features and show you my workflow by building a small sample infrastructure.

Michael February 9, 2025