Architectural case studies

The reasoning
behind the system.

Explore a system through the problem it addresses, its architecture, and the decisions that shape its behavior. Each study connects the design to my engineering contribution.

Explore the case studies View focused studies

System boundaries
Workflow design
Identity & trust
Integration patterns
Engineering decisions

Featured case studies

Look inside the engineering.

Customer workflows, distributed automation, and device trust—explored through their boundaries, lifecycles, and engineering decisions.

Distributed systems · Workflow orchestration

From scheduled job
to isolated execution.

What happens between scheduling a job and knowing that it finished—especially when a message arrives twice or a service restarts?

A case study in coordinating domain services, tracking run and execution lifecycles, and carrying tenant context into Kubernetes workloads.

Context: Multi-tenant enterprise automation
My role: Solution architecture & hands-on .NET engineering

Read the architectural case study

Follow the execution

Define & scheduleJob and timing rules
CoordinateRun, execution & Kafka events
ExecuteIsolated Kubernetes workload

Status events → run history & notifications

Tenant context and correlation connect the request to its execution history.

Device IAM · Multi-tenant architecture

A trust lifecycle for connected devices.

How should a device prove its identity, gain access, and change owners without carrying old permissions with it?

A case study in separating device identity, credentials, ownership, and policy—then connecting them through a shared trust control plane.

Context: Connected-device identity and access management
My role: Solution architecture & principal .NET engineering

Read the architectural case study

Architecture at a glance

DeviceTechnicianApplication

Authentication & tenant context

IdentityCredentialsOwnershipPolicy & risk

Lifecycle events & audit history

A shared trust layer across onboarding, access, transfer, and retirement.

Business workflows · Modular SaaS

Every enquiry needs
an owner and a next step.

When leads live in chats and spreadsheets, it is difficult to see who should respond—or which customer is still waiting.

An architecture for connecting enquiry capture, lead assignment, follow-up tasks, and pipeline visibility, with messaging providers behind replaceable integration boundaries.

Context: Customer enquiry and sales workflows
My role: SaaS architecture & .NET engineering
Stage: In development · Foundations implemented

Read the architectural case study

Watch the workflow on YouTube

Designed enquiry workflow