Marcus Biel.

Software architecture consulting · Architecture and code reviews

Review your software architecture or design a new system

I review existing code and help teams design new applications, services, and integrations.

You get the findings in writing, with the trade-offs and a recommendation you can act on.

I’m Marcus Biel. I lead the review and can work with your developers to put the design into practice.

Which decision do you need to make?

Perhaps an extension touches more of the system than you expected, or your team is weighing two designs and needs a second opinion.

Here are some of the questions a review can settle.

  • How would a new feature fit into our existing application?
  • Which dependencies make a seemingly small change difficult?
  • Which parts should be updated, restructured or replaced?
  • How should components, data and interfaces interact?
  • Which design best fits our requirements and the team that will maintain it?
  • What work needs to be done before the next phase of development?

I start with the question you need answered and the part of the system it concerns. That determines what sort of review or design you need.

Review an existing system or design a new one

Architecture and code review

A review can cover an application, a single component, or one decision your team wants to check before committing.

I focus the review on your question. That can include code structure, component responsibilities, data flows, interfaces, tests and error handling.

The review gives you a written account of

  • the question and the code I examined
  • what I found and why it matters
  • dependencies and questions still to resolve
  • the options for changing the software
  • which change I recommend making first

I’ll walk your team through the findings and answer questions about the code.

Design for a new system or feature

You may be planning a new application, adding a service, or extending a system that people already use.

I work through the requirements and propose how to structure the solution and how its parts will interact. The proposal takes account of your systems, operating environment and development team.

The design document covers

  • the main requirements and constraints
  • the proposed architecture and the reasoning behind it
  • what each component owns
  • how data moves between components
  • the alternatives I considered and their trade-offs
  • a first piece of work your team can build and test

Your developers can use that document to make decisions as they build.

What I review or design

A modular monolith or microservices?

Which parts need to ship independently? Who owns the data and who will run each service?

A team that releases together may only need clear module boundaries within one Java application. If teams need their own release schedules, I weigh the benefit against the extra work of running separate services. When services need to react to business events, I can design them with Spring Boot and Kafka.

How we reorganized a Java monolith around business rules

Data and interfaces

Where does the information originate, which system owns it and how is it passed on?

I trace how data moves from one system to the next, including how updates get through and what happens if a transfer fails.

More about APIs and system integration

Changing and testing the software

How easily can the team add features and verify existing workflows?

Depending on the question, I examine testability, dependencies and how business rules are represented in the implementation.

Rollout and operations

What does the software need for deployment and day-to-day operation?

I include those constraints wherever they affect the decision you need to make.

How we work together

  1. 1. Identify the question and the scope

    I start by asking about the decision your team faces and what you need to know to make it.

    We agree which parts of the system to examine, the depth of the review and which information is available.

    I’ll tell you which documents I need to see, what access I’ll need, and who I’d like to speak to.

  2. 2. Review the system or develop the design

    I work with the agreed code, available documentation and the people who know the business and technical context.

    Each finding identifies the part of the system I examined and spells out any assumptions or open questions.

    For a new design, I describe the proposed solution and explain why it fits your requirements and constraints.

  3. 3. Discuss the results and next steps

    You receive the agreed documentation, and I walk through the findings with you.

    Together we look at what the findings mean, what depends on what, and which changes are worth making first.

Findings your team can put to work

A finding identifies the affected part of the system, explains why it matters and sets out the available options.

An architecture proposal should explain how the solution can be built and what decisions still need to be made.

I document the reasoning, the assumptions, and any questions still to resolve so the design is useful to the person who picks it up next.

Your team can implement the recommendations. I can also join your developers or take on an agreed part of the work.

Who will review your architecture?

I’m Marcus Biel. I’ve worked with Java since 2001, both as a developer and as an architect.

A product owner once walked me through a solution he had designed. I thought the workflow was too complicated. In a conversation like that I want to know which step we could take out and still give the customer everything they need.

In a review I ask the people who use the software to walk me through a real case. What decision does it need to capture, and what do they call it? That is the name I want to find when I look for the rule in the code.

I work remotely with clients across Germany.

Marcus Biel
Marcus BielSoftware developer and architect

Frequently asked questions

How deep does an architecture or code review go?

I match the depth of the review to the decision you need to make.

Tracing one order through a pricing rule is a different job from reviewing dependencies across five services. We agree on the scope before work starts.

What documentation and access do you need?

For an existing application, I may need the relevant code, architecture notes, and information on storage, builds, tests, and deployment.

For an architecture design, I need the business goals, technical constraints and details of the systems involved.

I’ll tell you exactly what I need before I begin.

Can you review a prototype?

Yes. I can review a prototype’s structure and identify what it needs before people can rely on it.

That includes AI-generated code. I’ll start with the question you need answered, the stack, and the parts of the prototype that matter for the next release.

Take a prototype into production

Can our own team implement the recommendations?

Yes. I document the findings and walk your developers through the reasoning so they can make the changes themselves.

I can also arrange follow-up sessions, support the implementation, or take on some of the development.

What does a review or architecture design cost?

Cost depends on how much of the system I need to examine, the question I’m answering, and how much evidence I need to answer it.

The people I need to consult and the detail you need in the deliverables also affect the scope.

I confirm the scope with you in advance. I can then give you a quote or work to an agreed budget.

Which technical decision is holding you up?

Tell me what you’re building or changing and which options you’re weighing.

We can decide together whether a focused review or a new design would help.

Prefer to talk first? Call +49 171 1151013 or message me on LinkedIn.

Discuss an architecture project