services / software architecture

Freelance software architect – cloud architecture and modernisation

I design sound architectures and guide the way there – in the cloud on GCP, AWS and Kubernetes as well as in the incremental modernisation of grown .NET, Java or Go systems. Pragmatic, hands-on and with your team in mind.

starting point

Typical starting points

  • The monolith has grown for years, and nobody dares to make larger changes anymore.
  • Cloud costs keep rising, but nobody can say exactly what for.
  • Microservices were introduced – now there are more dependencies and coordination overhead than before.
  • Important architecture decisions are coming up, but an independent, experienced view is missing internally.
  • Deployments are manual, error-prone and block the teams.

deliverables

What I actually do

  • Architecture reviews with prioritised, actionable recommendations
  • Target architecture and migration path in realistic steps
  • Architecture Decision Records (ADRs) as a basis for decisions
  • Cloud architecture on GCP and AWS, Kubernetes and infrastructure as code
  • Incremental modernisation of legacy systems (strangler pattern)
  • Domain-driven design – shaping domains, teams and services
  • Setting up CI/CD and observability

Architecture that fits your organisation

An architecture is only as good as its feasibility. The most elegant target architecture doesn’t help if your team can’t operate it or if getting there means two years of standstill. That’s why I look at technology, teams and business goals together – and develop solutions that can be reached step by step.

My background as a developer helps: I know the reality in the code and which decisions hold up in daily work versus those that only look good on a whiteboard.

Architecture review

In a review I analyse your system from several angles: structure and dependencies, data storage, scalability, security, operations and development process. I talk to the people who build and run the system, because the most important insights are rarely in the code alone.

The result isn’t a hundred-page document but a clear assessment with prioritised recommendations: what’s critical, what gives quick wins, what can wait? Important decisions are captured as Architecture Decision Records so they stay traceable.

Cloud architecture

Whether Google Cloud or AWS: I design cloud architectures that are secure, observable and cost-efficient. That includes Kubernetes where it makes sense and managed services where they reduce operational effort. I describe infrastructure as code with Terraform so environments are reproducible and changes are traceable.

I pay particular attention to cost: the right services, proper sizing and transparency about consumption often reduce cloud spending noticeably without compromising stability.

Modernising legacy systems

Many companies depend on systems that have grown over years – often in .NET or Java. A complete rewrite is risky, expensive and usually takes longer than planned. So I rely on incremental modernisation following the strangler pattern: using domain-driven design we identify sensible seams, extract parts deliberately and move them piece by piece into a modern architecture – while the existing system keeps running and your business never stops.

stack

Technologies

  • Core
  • Strong
  • Familiar

Architecture & backend

8
  • Software architecture – Core
  • Domain-Driven Design – Core
  • Microservices – Core
  • Legacy modernisation – Core
  • .NET / C# – Strong
  • Go – Strong
  • Java / Spring – Strong
  • Event streaming (Kafka) – Familiar

Cloud & platform

8
  • Google Cloud (GCP) – Core
  • Kubernetes – Core
  • Terraform / IaC – Core
  • AWS – Strong
  • CI/CD – Strong
  • Observability – Strong
  • Azure – Familiar
  • VMware vSphere (SDK) – Familiar

process

How we work together

Arrive on-site first, then deliver efficiently remote – anywhere in Germany and the DACH region.

  1. 01

    Intro call

    30 minutes, free – goals, scope and whether we're a good fit.

  2. 02

    On-site onboarding

    A few days with your team to learn people, systems and domain.

  3. 03

    Remote delivery

    Mostly remote, with fixed rituals and visits as needed.

  4. 04

    Handover & enablement

    Documentation and knowledge transfer – your team takes over.

projects

IT training2011–2017

Automating training infrastructure (Fast Lane)

C#-based control and automation of a large environment of virtual and physical machines for IT training – as software developer and system architect.

  • .NET
  • C#
  • VMware vSphere
  • Python
  • CI/CD

faq

Frequently asked questions

What does an architecture review cost?

A focused review works well as a fixed-price package. Scope and price depend on system size and the question at hand – I clarify both with you in a short call.

Do we have to rewrite everything to modernise?

No, and usually you shouldn't. I favour incremental modernisation: new features are built in the new architecture, old ones are replaced step by step, and the system stays in operation throughout.

Are microservices the right choice for us?

That depends on team size, domain and operational maturity. A well-structured modular monolith is often the better choice. I help you make this decision deliberately and with good reasons.

Do you implement the architecture yourself?

Yes. I'm an architect who writes code. Especially in the early phase I like to build the critical parts myself and support your team in implementing the rest.

contact

Let's talk about your project.

Tell me briefly what it's about – I'll get back to you within 1–2 business days.