Preparing the decision
Based on the business objective, we define measurable expectations for capacity and availability. These are non-functional requirements (NFRs). I use C4 diagrams to clarify system boundaries and key connections.
04 / SERVICE
Suppliers recommend different solutions, the team sees different risks and the decision may shape operations for years. I evaluate alternatives against agreed criteria and explain the assumptions and trade-offs behind them.
01 / SITUATION AND SOLUTION
I consider business objectives, effort and operations together. I design architectures, APIs and event-driven integrations for Java and Spring Boot systems.
Professional backgroundDo you need to choose between different supplier proposals?I compare designs and proposals against common criteria: business fit, effort, operations and dependencies.
Does your team need support from an experienced architect?I review the planned architecture, integrations and technology decisions. I distinguish supported claims from open questions.
Does an earlier technical decision need rethinking during implementation?I evaluate changing requirements alongside earlier decisions. I can provide a one-off opinion or regular technical discussions.
02 / WORKING TOGETHER

Based on the business objective, we define measurable expectations for capacity and availability. These are non-functional requirements (NFRs). I use C4 diagrams to clarify system boundaries and key connections.
I use trade-off analysis to compare alternatives in terms of performance, security, modifiability and operational effort. Where necessary, we test critical assumptions with a focused technical prototype.
I record the options, rationale and consequences in an architecture decision record (ADR). This preserves the reasoning and assumptions behind the decision.
With an API-first approach, we define in advance what data systems exchange and how they report errors. I recommend automated architectural checks (fitness functions), for example to detect prohibited dependencies between modules.
I select methods to suit the decision. The evaluation considers the team's experience, existing technology and supplier conditions. My involvement during implementation is agreed separately.
03 / DELIVERABLES
We can discuss the recommendation with your team and suppliers. During implementation, I can provide a one-off review or regular support agreed in advance.
04 / GETTING STARTED
05 / FREQUENTLY ASKED QUESTIONS
Yes. I also review individual designs, proposals or technical decisions. We agree the time required based on the task and materials to be reviewed.
Consulting usually focuses on defined technical questions and decisions. If a targeted development task is also needed, we agree its scope separately.
Yes. We can review plans and questions together. We clarify decision-making authority and responsibilities at the start of the collaboration.
We agree meeting frequency, materials to review and response times based on the specific decisions and tasks. Recommendations and open questions are documented in writing.
Briefly describe the options you are considering and what makes the choice difficult. We can discuss which evaluation would help you move forward.