Software architecture and system design
Why architecture is a business decision
The architecture of a piece of software defines how its parts work together: which components exist, where data is stored, how systems communicate with each other and how the application is operated. These decisions are made early and can only be corrected later at great expense. They determine how quickly new features can be built, what operation costs and how well the software copes with load peaks, outages and attacks.
We design architectures for new systems and assess existing ones before they are extended or modernised. Our principle: as simple as possible, as flexible as necessary. Not every system needs microservices and elaborate container orchestration – a well-structured, modular application is often the more economical and more robust solution.
How we support you
Architecture for new systems. Components, data model, interfaces and operating concept – tailored to user numbers, data volumes, security requirements and your budget.
Assessment of existing systems. We analyse code, dependencies and infrastructure and show where the risks lie and which measures are worth taking first – as a basis for extension or modernisation.
Technology decisions. Programming language, framework, database, hosting: we weigh up the options transparently so that your decision still makes sense years later.
Scaling and operations. Containerised applications, automated deployments and background processing that grows with the load – aligned with the right hosting architecture.
Our principles for long-lived systems
We rely on proven building blocks that are maintained over the long term: Ruby on Rails and PostgreSQL, Docker and Kamal for automated deployments via GitLab CI, plus error monitoring on our own infrastructure. We assess new technologies by their benefit for your project, not by the hype. We also run these tools in our own products.
Good architecture often shows in the details. In Stundenplan-Digital, every school lesson is a separate calendar event with a stable ID. This means a single lesson can be changed without breaking the whole series in families' calendars. Decisions like these are inconspicuous, but save a great deal of effort and frustration later on.
From our projects: a platform that has grown since 2015
The PicturePartners event photo platform, on which the ClicClic brand is also built today, now spans six platforms: embedded Linux, iOS, Android, web, desktop and cloud. Its architecture has supported every turn in the business model – including the move from a custom camera box with a tailored embedded Linux to native apps that control professional cameras directly. We advised PicturePartners on this technology decision. Find out more in the ClicClic case study.
How we proceed
- Discussion of goals, constraints and existing systems
- Analysis of requirements, risks and options
- Architecture design with clearly justified decisions
- Implementation, guidance and regular reviews
- Discussion of goals, constraints and existing systems
- Analysis of requirements, risks and options
- Architecture design with clearly justified decisions
- Implementation, guidance and regular reviews
Frequently asked questions about software architecture
Monolith or microservices?
For most applications at small and medium-sized businesses, a well-structured monolith is the better choice: it is easier to develop, test and operate. Microservices pay off when several teams work independently of each other or individual parts need to scale very differently. A modular monolith with clear boundaries keeps that path open for you.
When is it worth assessing the existing architecture?
Before a major extension, when changes take longer and longer, when the application slows down under load or before you take over a system from another provider. New security requirements, such as those of Germany's NIS2 Implementation Act (NIS2-Umsetzungsgesetz), are also a good reason. The assessment shows what is worth tackling first – and what you can safely leave as it is.
How does an architecture stay future-proof?
Through clear boundaries between the parts of an application, automated tests and deployments, and proven technologies that are maintained over the long term. It is just as important to review decisions regularly: what was right at the start may no longer fit after a few years of growth.
Hyperscaler or hosting in Germany?
Both have their place. We run our own products at Hetzner in Germany; the PicturePartners event photo platform uses storage in the AWS cloud. Which solution suits you depends on data protection, load profile, required services and costs. Find out more on our page about architecture and planning for operations.
How much does architecture consulting cost?
That depends on the scope – from assessing a single application to designing a new platform. In a free initial consultation, we clarify what you need. What the costs of the subsequent project depend on is explained in our guide How much does custom software cost?.
Didn't find your question?Get in touch
Whether it is a new system or an application that has grown over time: we show you where the risks lie and what a sound solution looks like.