Solutions & Experiences

Software Development

One size doesn't fit all

For many of our customers, one-size-fits-all solutions from large product manufacturers, for example, are not enough to implement their digital strategy. They need to combine a wide variety of systems and merge them into a complete system or create completely individual solutions. This is exactly where we come in and support you in implementing the individual requirements of your digitization strategy.

Your contact person
Jochen Binder
Head of Backend & Data Solutions
Your contact person
Jannik Egger
Head of CC Frontend & Apps

Our services in the area of software development

  • Individual software development on a very high quality level. Our Scrum teams are trained to bring very high quality software into production quickly. We achieve this through high test coverage and automated deployment. We support our customers in prioritizing their requirements. In this way, we jointly guarantee a very fast benefit and the use of the newly created features for our customers' clientele.

  • Modern architectures: Microservices, API-first, Cloud Native and Headless, these are the keywords that drive us forward. Our teams encapsulate technically distinct software parts from each other (Domain-Driven Design) and thus bring decoupled systems into operation, which can be replaced independently of each other in case of changes.

  • Migration of monolithic systems into modern microservice architectures

  • Architecture assessment and architecture consulting

Do you have individual requirements for your digitization strategy that no product can cover? Do you need to integrate many systems into one worldwide high-availability system? International alignments are a matter of course for you and you need a partnership that is familiar with such challenges and supports you? We develop custom-fit solutions for you or combine products to create a complete system - for you and your customers.

This is how we proceed - from MACH to REST

We work with a very modern architectural approach - the MACH architecture. MACH stands for microservices, API-first, cloud-native and headless. Microservices are parts of the business logic that encapsulate requirements and are brought into operation independently of one another. We use Domain-Driven Design (DDD) to determine the domain-oriented sections of the business logic. Api-first describes services, and products, such as an e-commerce system, which can be completely controlled via an API.

All the services we connect are tailored to the cloud provider. In turn, they use services and services (SaaS) that offer a scalable overall system that fits exactly (cloud-native). To enable a very modern web front end or even the connection of a mobile app to the backend services, a headless approach is chosen. The various clients can thus select the data via REST or GraphQL, for example, and display it according to the touchpoint.

Creation

Overall system architecture

  • Requirements analysis in various workshops

  • NFR (Non-Functional Requirements): Scenarios are used to describe the quality characteristics of the system in terms of changeability, usability, efficiency, functionality, transferability.

  • Functional requirements are put into a meaningful order with the help of story mapping

  • Development of a caching strategy

  • Scalability and resilience of the system

  • Interface analysis

  • Data flows are captured

  • Sizing of the systems, description of scaling scenarios

  • IAM (Identity Access Management) for example with Keycloak

  • ... further specific individual requirements are defined!

Implementation

Prioritized backlog

  • We very often work with our customers using the MVP (Minimum Viable Product) approach. This means that in order to deliver fast customer feedback and added value, we choose the smallest possible feature set with which we can quickly go into production.

  • The critical and important things, which deliver the most added value or minimize risks, are implemented first.

  • With agile software development, diva-e teams are constantly working on optimization.

  • The deployment of the artifacts starts at the latest after each iteration (sprint cycle).

Procedure

How we work

Programming languages used, products, services

  • We work with custom-fit architectures and select the appropriate systems together with our customers.

  • Individual requirements are implemented in the form of microservices or serverless functions.

  • We combine SaaS and PaaS solutions with the help of a MACH architecture. We are partners of Microsoft Azure and Amazon Web Services (aws) and combine the appropriate platform or service for your system.

  • We select the appropriate programming language for the system, our customers and the development teams involved: Java, Kotlin or .net are often used, but also Golang or Python.

Automated Deployment

  • CI/CD pipeline: automated deployment from the beginning of development to live and in operation.

Self-scaling systems and operation

  • We work with our customers from the very beginning on the availability requirements of the target system to ensure cost-efficient operation.

Do you have any questions? Get in touch with us!

Your contact person
Jochen Binder
Head of Backend & Data Solutions
Your contact person
Jannik Egger
Head of CC Frontend & Apps

Software Development Glossary

Microservices

API-first

Cloud-native

Headless

Agile software development

MVP - Minimum Viable Product

NFR – Non-Functional Requirements

Serverless Functions

Resilience

Platform as a service (PaaS)

Identity Access Management (IAM)

REST

GraphQL

Frequently asked questions in connection with Software Development

What differentiates MACH from pure microservice architecture?

What is the advantage of a MACH architecture over an enterprise solution?

How do you ensure that features get up and running quickly without compromising the system?

What happens if a particular service fails, is the entire system then no longer available?

Top Clients