Cloud-native – At Home in the Cloud

Cloud-native applications are designed specifically for operation in the cloud. They differ from classical server applications in several respects: Their configuration is loaded via cloud infrastructure and can be changed at runtime. In addition, cloud-native applications are dynamically scalable and support complex deployment patterns such as canary releases or blue/green deployments.

To develop cloud-native software, ConSol engineers cooperate closely with OpenShift experts, monitoring consultants and the operations team. Our interdisciplinary communication results in cloud-native applications especially built for this environment. Thus, engineering actively provides metrics for monitoring the application. This allows for automatically detecting the failure of individual instances in order to fix it quickly without affecting the entire system.

Advantages of Cloud-native Software


Unlimited Scalability

Cloud-native applications can use your provider's resources to any amount they require it. On this basis you can grow with the occurring load – or shrink if necessary.


Maximum Available

For maximum reliability, application instances in the cloud can be easily distributed across multiple data centers. Sophisticated deployment procedures allow seamless and low-risk live updates.



Whether public or private cloud, the future belongs to cloud-native development. Today, a cloud-native application is a great competitive advantage – tomorrow it may already be the de facto standard.

Cloud Computing: Technological Mainstays

Cloud environments provide the infrastructure for centrally managing the configuration for all applications. Custom Resource Definitions e.g. can be defined for Kubernetes. Cloud-native applications are able to use their infrastructure to load their configuration and react dynamically to configuration changes.

Cloud environments provide the infrastructure for horizontal autoscaling. Cloud-native applications are able to use this infrastructure. In other words, they provide metrics that can be used to determine the required number of instances. And they also support dynamic load balancing.

Cloud environments provide the infrastructure to simultaneously run multiple versions of an application and dynamically distribute traffic across different versions. This enables complex deployment patterns such as Canary Deployments or Blue/Green Deployments. Cloud-native applications support these deployment patterns.

In the cloud, building and testing processes can be significantly accelerated and improved. The Docker image is the relevant software artifact that delivers software with all its dependencies. In the virtual infrastructure, the testing process can create any number of application environments that are almost identical to the production environment. If these environments are defined as infrastructure code, changes to the infrastructure can also be automatically tested via the CI/CD process.

Cloud environments provide a sophisticated monitoring infrastructure to evaluate application log data, metrics, and tracing information. Cloud-native applications fit into this infrastructure and actively provide metrics about their internal state.

Cloud environments are designed for largely automated operation. Incorrect instances are automatically restarted. In case of overload, instances are automatically terminated and moved to other hardware. This dynamic implies, that individual failed calls within a service landscape are the normal case and do not only occur in exceptional situations. Cloud-native applications use modern communication paradigms such as asynchronous communication and circuit breakers and automatically return to a consistent state after failed calls, without affecting the complete system.

In dynamic cloud environments, it is often not feasible to address services via fixed IP addresses or domain names. Cloud-native applications use dynamic service discovery mechanisms for communication and can handle dynamically changing infrastructure.

The ConSol Cloud Offer for Enterprises

Project Profiles

We love it when requirements are high, because ConSol stands for technological excellence and practical expertise. We draw on three decades of cross-industry project experience – in medium-sized companies as well as in DAX corporations and other heavyweights. We support you in important software architecture decisions and put your cloud computing solution on a solid foundation. Here is a small overview:

Branch: Automotive

Project content: Application for market research and sales forecasting of automotive components.
Technologies: React, SpringBoot, MSSQL

Branch: Authority

Project content: Customer portal in a modern design for the provision of services for private persons and companies.
Technologies: Angular, SpringBoot

Branch: IT

Project content: Administration GUI for an Enterprise Cloud Software.
Technologies: React

Branch: Automotive

Project content: B2B application for the detailed comparison of vehicles and their equipment features.
Technologies: Angular, JavaEE, MongoDB

Branche: Telecommunications

Project content: Classic customer self-care portal for a telecommunications provider.
Technologies: Backbone.js, SpringBoot, JWT

Branch: Authority

Project content: Customer management for a municipal authority.
Technologies: Angular, Grails, ConSol CM

Branch: Automotive

Project content: Administration GUI for an application for provisioning vehicles.
Technologies: Angular, JavaEE, Microservice

Branch: Telecommunications

Project content: Application for market research and sales forecasting of automotive components.
Technologies: Microservice, Spring, REST, SOAP, Citrus

Branch: Telecommunications

Project content: Development of an integration platform for the exchange of Smart Meter data with SAP.
Technologies: Weblogic, SpringIntegration, SOAP, Messaging, Citrus

Branch: Automotive

Project content: Online interfaces for the provisioning of new vehicles.
Technologies: Microservice, REST, MQTT

Branch: Automotive

Project content: Gateway for the internet communication of vehicles.
Technologies: Microservice, REST, SOAP, MQTT, Citrus

Branch: Telecommunications

Project content: Web-based mail and messaging platform.
Technologies: SOAP, Messaging, SMS, Citrus

Branch: Telecommunications

Project content: Online interface for data exchange with telecommunication providers.
Technologies: SOAP, Spring, Citrus

Branch: Retail
Solution: Business service and system monitoring based on Nagios

pbb Deutsche Pfandbriefbank
Branch: Finances
Solution: End-to-end application monitoring with Sakuli

it@M, central IT service provider for the City of Munich
Branch: Public Administration
Solution: Open Source Monitoring with OMD

Branch: Telecommunications
Solution: Future-proof monitoring on Nagios basis

Statutory Health Insurance Association of Lower Saxony
Branch: Public Administration
Solution: Seamless IT monitoring of the server landscape

Branch: Automotive

Project content: Advancement and transition to AWS of containerized microservices for processing vehicle data
Technologies: Java, Spring Boot, Java EE, OpenShift, AWS, Kubernetes, Terraform, Ansible, Citrus, PostgreSQL, Oracle Database

Branch: Automotive

Project content: New development of a scalable API gateway and caching services as containerized microservice
Technologies: Java, Spring Boot, OpenShift, Redis

Branch: Automotive

Project content: New development of containerised microservices for usage-based service contracts
Technologies: Java, Java EE, OpenShift, Citrus, TypeScript, Angular, PostgreSQL

Branch: Automotive

Project content: New development of containerised microservices for vehicle allocation
Technologies: Java, Java EE, Spring Boot, OpenShift, PostgreSQL

Branch: Automotive

Project content: Reference implementation for Big Data software projects for operation on a container cluster
Technologies: Apache Spark, OpenShift, Apache Kafka, Citrus

Branch: Automotive

Project content: Self-developed standard solution for backups of persistent volumes in container clusters
Technologies: Java, Spring, OpenShift, Restic, Citrus

Branch: Construction

Project content: Cloud-supported multi-client system for a SaaS software for quality management
Technologies: AWS, Kubernetes, Java, Keycloak, Terraform, Ansible, Gitlab CI, Citrus, Sakuli



We share our know how. Read more on our open source blog!


Oliver Weise