VSHN AppFlow

This is a preview - VSHN AppFlow isn’t available yet.

We engineer the best-matching development and deployment workflow for your application by combining our expertise and best-practices with our products like VSHN AppOps, APPUiO Managed, APPUiO Cloud and services from our Application Catalog.

Ultimately we help you to be fast to write code and bring it into production where it brings the most value.

Offering Overview

VSHN AppFlow consists of several building blocks which can be (conditionally) mixed-and-matched. All parts combined is your one-stop solution to bring code from development to production as fast and secure as possible.

Building Block Kind Description

Continuous Integration Pipeline (CI) Engineering

Consulting

Best-practice CI pipeline engineering, based on pre-engineered blue-prints and templates which are continuosly kept up-to-date

Continuous Delivery (CD) Engineering

Consulting

Continuous delivery process engineering, matching our expertise in delivering application to the cloud leveraging our AppOps platform

Containerizing and Packaging

Consulting

Containerizing and Packaging (Helm Charts) of application with pre-engineered blue-prints and templates which are continuosly kept up-to-date, leveraging our experience of containerizing hundreds of applications

DevSecOps

Consulting

Security measures start in the code. We help with security by leveraging possibilities directly in the CI/CD pipeline and containerizing.

Continuous Integration Pipeline (CI) Engineering

Continuous Integration (CI) is the art of building and testing code on every push to a remote Git repository. This can include simple code checks, unit-tests or even full-blown end-to-end tests with all the bells and whistles. How an application has to be built and what needs to be tested heavily depends on the application and is different for each and every use-case.

Such processes are the backbone of application development. CI pipelines should never break, neither because of the pushed code, nor because something is wrong with the pipeline itself, as this can bring the whole application development cycle to a halt. And they should be fast for a continuous feedback to the developer.

In the end, CI pipelines are also application which needs maintenance and kept up-to-date.

With our expert expertise we engineer CI pipelines with best-practices, pre-engineered blue-prints and templates which we continuosly keep up-to-date.

Continuous Delivery (CD) Engineering

After building and testing an application, it needs to be delivered to the hosting environment. This process is called delivery, and with continuous delivery, that process happens continuosly, automated and with clearly defined steps.

Delivery can happen to pre-defined environments like "development", "staging", "integration" and "production" or it can even happen to dynamic environments which are automatically created and removed depending on conditions - this heavily depends on the use-case. A good delivery process also helps with concepts like staged rollout or A/B testing and provides a fast feedback on the delivery process.

As with CI pipelines, CD pipelines are software which needs maintenance and kept up-to-date.

With our expert expertise we engineer CD pipelines with best-practices, pre-engineered blue-prints and templates which we continuosly keep up-to-date.

Containerizing and Packaging

For an application to run in a Cloud Native environment it needs to be packaged into a container image and usually made available to install as a Helm Chart. This can be a very complex process - depending on the requirements of the application. Containerizing an application needs to be a very fast process so that it doesn’t slow down other processes like the CI pipeline, it has a lot of room for improvements to make it fast. Helm Charts should be as flexible as needed and have a good quality for proper deployments.

With our expert expertise we engineer containerizing processes and Helm Charts with best-practices, pre-engineered blue-prints and templates which we continuosly keep up-to-date.

DevSecOps

There are several measures to be taken for secure software processes. We can directly integrate several lines of defense while developing software:

  • Keeping dependencies up-to-date by directly creating Pull-/Merge-Request should there be a new version available

  • Having a SBOM (Software Bill of Materials) to know what dependencies are used where and in which versions and what artefacts are available after building the application

  • Scanning of container images for vulnerabilities and keep the base images up-to-date

  • Signing of container images and build-artifacts for later verification