Software Architect

Architecture decisions that are written down, argued against the quality requirements that matter to the business, and still make sense after handover. Part-time, close enough to the code to build what I design.

What I do

  • Architecture assessment

    A review of an existing system against the quality goals that matter to you: performance, reliability, security, maintainability, cost. We agree the goals, test the design against concrete scenarios, and you get the risks, the trade-offs and a prioritised list of fixes.

    Fixed scope. The usual place to start.

  • Target architecture and modernisation roadmap

    Service boundaries, data ownership and integration style (synchronous, asynchronous, event-driven), with a migration path that keeps the business running: strangler-fig extraction, parallel runs, no big-bang cut-over.

  • Architecture documentation

    An arc42 document with C4 diagrams and a log of Architecture Decision Records, so the reasoning survives the people who made it.

  • Fractional architect

    A few hours a week to review designs, guide teams and keep decisions consistent across services. Includes cloud cost review.

Standards, not a house method

Your team can keep using them after I leave.

ISO/IEC/IEEE 42010
What an architecture description must cover: stakeholders, their concerns, and the views that answer them.
arc42
The structure for the documentation, from goals and constraints to decisions and risks.
C4 model
Diagrams at fixed levels of zoom: system context, containers, components.
Architecture Decision Records
One short record per decision: the context, the decision, and its consequences.

Fits when

A large change is coming: a monolith split, a rewrite, a cloud move, a jump in scale. Or the architecture lives only in a few people’s heads.

What it produced

Clients are anonymised. The SaaS engagement in full.

3 services
extracted from a monolith over 6–12 months, with no planned downtime.SaaS company
Around 10–15%
less cloud spend, from rightsizing and optimising applications and data processing.SaaS company
1 model
for authorization, in place of role checks scattered across the code.SaaS company
2+ of 3+
proofs of concept on microservices and BPMN orchestration taken to production, in a legacy modernisation.Telecom operator

Send what is changing, what worries you about it, and the timeline.

ante.rados@delmisoft.hr