Available for new roles

Muzaffer Berk

Berkmen

Fullstack Software Engineer

Distributed Systems Architect

I build software that stays reliable once it ships — clear boundaries, observable behavior, and systems made to last.

0Years Building
0High-Traffic Platforms
0Uptime SLA
0Production Projects
scroll
01The Engineer

Systems that hold
under pressure.

2+ years shipping production backend systems — across enterprise platforms, health infrastructure, and e-commerce serving millions of users.

I specialize in distributed architectures — designing the boundaries, messaging patterns, and data consistency strategies that make microservices predictable at scale.

Currently exploring new opportunities — open to senior backend and distributed systems roles where scale, reliability, and AI infrastructure are the hard problems.

Open to Work
Backend
.NET CoreASP.NET CoreC#Entity Framework CoreSignalRDapper
Databases
MSSQLPostgreSQLMySQLMongoDBRedis
Infrastructure
RabbitMQDockerCI/CDJenkinsGitxUnit
AI & Intelligence
OpenAI APIRAGPrompt EngineeringOllamaML.NETClaude APICursor
02Systems Built

Production systems
at real scale.

Not demos. Not tutorials. Systems that process thousands of transactions daily, serve millions of users, and maintain uptime SLAs under real pressure.

01ecommerce

Funpay

(funpay.com)

B2C E-Commerce Platform — Russia's Leading Gaming platform

150+

API Endpoints

7

Shared Services

Asp.Net CoreC#MSSQL.Net Core+3
View details →
02platform

Kansuk Ilac

Designed Product tracking software system all the way through

Pharmaceutical Industry

Platform Type

Layered Architecture

Architecture

Asp.Net CoreAsp.NetC#Javascript+3
View details →
03platform

Kansuk Ilac

Vehicle tracking fleet software system for the owners and employees

MVC

Web Interface

0%

Error Rate

Asp.Net CoreAsp.NetC#Javascript+3
View details →
04platform

Kansuk Ilac

(herguniyihisset.com)

Development of multiple health products

Healthcare

Platform

Full-Stack

Stack

Asp.Net CoreAsp.NetC#Javascript+5
View details →
05ecommerce

Trend Print

E-commerce platform for a company that manufactures printing equipment

12

API Counts

Germany

Market

Asp.Net CoreAsp.NetC#Javascript+5
View details →
06platform

Gaming Platform

Multi Turkish Gaming platform

22+

API Endpoints

92.72%

Uptime

Asp.Net CoreAsp.NetC#Javascript+8
View details →
03Engineering Philosophy

How I decide
when building.

Engineering principles are not decisions made on the spur of the moment. They involve designing systems that allow for development from the very beginning.

01

Design for Scale Before Scale Arrives

A design that is as understandable as possible, with details serving as elements that add variety to this simplicity.

Technical debt is a constant in architectures that scale on demand. The infrastructural backbone established during the initial design phase — how data is partitioned, how state management is decoupled from services, and asynchronous data flow patterns — directly determines whether the system will withstand peak loads or fail.

service boundariesstatelessqueuesdata ownership
02

Failure Is a Feature, Not an Exception

Errors are inherently part of the system; those that indicate persistence, however, are a major problem.

Every software system that is designed will inevitably encounter issues. The real question is whether these issues are simple, fixable problems, or part of an ongoing chain of failures. Concepts such as bulkheads, circuit breakers, and graceful degradation help us determine whether a situation is a full-blown disaster or something that could have been prevented.

timeoutssafe retriesqueuesisolation
03

You Cannot Fix What You Cannot See

Traces, metrics, and logs are essential for any piece of software.

Observability is not a plugin to be integrated after going live; it is a design constraint that must be followed from day one. Structured logs, end-to-end distributed tracing, and RED metrics transform an opaque black box into a transparent and manageable system.

latencyerror ratequeue depthslow queries
04

Complexity Is a Liability

The best architecture is the one you can explain and design.

The quality of a system is measured by how explainable and manageable it is. CQRS, microservice architecture, and event-driven structures are not a destination — they are methods. Every abstraction without a sound reason adds weight. A plain monolithic design on solid ground is stronger than a service mesh that has lost control and is full of blind spots.

explainabilitycqrsevent-drivenmonolith
04AI & Intelligent Systems

Systems that
collaborate with intelligence.

Not using AI as a feature — integrating intelligence as infrastructure. Embedding pipelines, agent orchestration, and local inference as production concerns.

RAG Pipeline Architecture

production

Retrieval-Augmented Generation systems connecting LLMs to proprietary knowledge bases. Embedding pipelines, vector store integrations, and context-window management for domain-specific applications.

OpenAI APIpgvectorsemantic searchembeddings

Agent Orchestration

production

Multi-agent systems where specialized agents handle distinct tasks coordinated by an orchestrator. Built for customer support automation and internal tooling with function calling and tool use.

OpenAI Assistantsfunction callingtool usestate machines

Local Model Inference

experimental

On-premise LLM deployment using Ollama for air-gapped environments. Evaluated Mistral, LLaMA, and Phi families for domain-specific tasks with GGUF quantization strategies.

OllamaMistralLLaMA 3GGUFquantization

AI-Integrated Backends

production

Designing .NET backend services that orchestrate AI workflows as first-class infrastructure. Streaming responses, async queuing for inference, and cost-aware routing between providers.

Claude APIOpenAI APIasync queuingstreamingcost routing
Architecture Diagram

RAG Pipeline

Retrieval-augmented generation: from a user query to a grounded response.

User Query
Embed Query
Vector Store
Retrieve Docs
Build Context
LLM
Response
Input/Output
Processing
LLM
Vector Store
05Under the Hood

Async. Resilient.
Built to fail gracefully.

Not just built to work — built to keep working when things go wrong. Event-driven order pipeline: how messages flow, retries happen, and consistency holds without tight coupling.

Live — Event Pipeline
Event Pipeline — Live Simulation
Runtime — Queue Metrics
rabbitmq@commerce-node
$
06Contact

Let's build
something resilient.

If you're building systems that need to survive production — distributed, resilient, and actually shipped — let's talk.

contact — berk@systems
Welcome. Type help to see available commands.
$ help
Available commands:contact— Email addressgithub— GitHub profilelinkedin— LinkedIn profilestatus— Current availabilityclear— Clear terminal
$
M. Berk Berkmen2026 — Built with Next.js