Software Engineering

Software Architecture & System Design

.NET backend architecture, the microservice-or-monolith decision, and a domain model that survives growth.

Software architecture is the design that decides how a system is split into parts, how those parts talk to each other, and which choices cannot be reversed later. GG Tech's Software Architecture & System Design service produces that design for .NET backends: the domain model, the service boundaries, the microservice-or-monolith decision, and the reasoning behind each technology choice — written down so your own team can carry the system without us.

GG Tech Teknoloji estimation modelSoftware Architecture & System Design · Last reviewed: 2026-06-13
Typical team1 architect + 1 senior developer
Calendar band38 weeks
Phase split35% current-state analysis · 35% domain model & decisions · 20% prototype & validation · 10% handover

What grows the budget

  • Number of source systems
  • Domain complexity
  • Undocumented behavior
  • How much the in-house team must take over

Signs of underbudgeting

  • Decisions with no written rationale
  • The architecture lives in one person's head

These are GG Tech Teknoloji planning bands, not a quote — we do not publish prices. Every project is different, so the bands are deliberately wide; they assume a senior, focused team and typical scope, and your project is estimated individually.

How we work

  1. 1

    Current-state analysis

    We read the running code and the database rather than the documentation: what calls what, where each record actually lives, and which behavior nobody wrote down.

  2. 2

    Domain model and boundaries

    Entities, ownership, and transaction boundaries. This is where a service boundary is either drawn correctly or paid for later.

  3. 3

    Architecture decisions on the record

    Monolith or microservices, synchronous calls or queues, which store for which data — each decision written with the alternatives it beat and the cost it carries.

  4. 4

    Incremental rollout

    The design ships in slices that run in production. An architecture nobody has executed is a document, not a system.

What we deliver

Software Architecture & System Design

.NET backend architecture, the microservice-or-monolith decision, and a domain model that survives growth.

Our team combines domain expertise, modern engineering, and research-driven design to build solutions that scale. We work in focused sprints with clear milestones and measurable outcomes.

Architecture document with context, container, and component views
Domain model and data dictionary
Decision record (ADR) including the rejected alternatives
API contracts as OpenAPI specifications
Technology selection rationale
Phased rollout plan

Proof from production

6

applications on one architecture

63

admin modules

12

weeks to production

Figures from the Çekmeköy Municipality central system, read from the codebase rather than estimated.

Read the case study: Çekmeköy Belediyesi

Last updated:

Let's Build Something Great Together!

However, we approach things a bit differently around here.

Get Contact