01ecommerce
10+
Integration Points
99.95%
Uptime
.NET CoreC#ASP.NET CoreMSSQL+7
2024 — 2026
View details →
Available for senior roles
Mehmet Özberk
Esentürk
Senior Backend Engineer
Distributed Systems Architect
I architect distributed systems that hold under pressure — scalable, observable, and built to last.
0Years Building
0High-Traffic Platforms
0Uptime SLA
0Production Projects
scroll
01The Engineer
Systems that hold
under pressure.
7+ years shipping production backend systems — across enterprise platforms, logistics 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 API
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.
02ecommerce
180+
API Endpoints
8
Shared Services
.NET CoreC#ASP.NET CoreMSSQL+7
2024 — 2026
View details →
03ecommerce
Outlet
Platform Type
0%
Oversell Rate
.NET CoreC#ASP.NET CoreMSSQL+7
2024 — 2026
View details →
04ecommerce
Vestel Germany
International B2C E-Commerce — DACH Market
DACH
Market
Amazon
Marketplace
.NET CoreC#StripeChannable+2
2024 — 2026
View details →
05ecommerce
Nordic
Market
B2B
Platform
.NET CoreC#StripeSAP+2
2024 — 2026
View details →
06platform
10+
Carrier Integrations
Microservices
Architecture
.NET CoreC#ASP.NET CoreRabbitMQ+4
2021 — 2024
View details →
07platform
Workbook
ERP, CRM, WMS & Workflow Automation Suite — Odak Innovation
3+
Web Platforms
Full-Stack
Stack
.NET CoreC#MSSQLXamarin+2
2019 — 2021
View details →
08platform
ICMS / TV8 HBBTV
Smart TV & Interactive Broadcast Platform for TV8
HBBTV
Standard
WebSocket
Streaming
ASP.NET CoreJavaScriptHTML5CSS+3
2018 — 2019
View details →
03Engineering Philosophy
How I think
about systems.
Engineering principles are not rules — they are decisions made early that propagate through every layer of a system.
01
Design for Scale Before Scale Arrives
Horizontal by default, vertical when forced.
Systems that scale reactively always carry technical debt. Architecture decisions made at inception — data partitioning, stateless service boundaries, async communication patterns — determine whether a system bends or breaks under load.
horizontal scalingstatelessshardingevent-driven
02
Failure Is a Feature, Not an Exception
Circuit breakers, not optimism.
Every distributed system experiences partial failure. The question is whether the failure is contained or cascading. Bulkheads, circuit breakers, and graceful degradation are the difference between an incident and a disaster.
circuit breakerbulkheadgraceful degradationchaos
03
You Cannot Fix What You Cannot See
Traces, metrics, logs — all three or none.
Observability is not a feature added post-launch — it is a design constraint from day one. Structured logs, distributed tracing, and RED metrics transform a black box into an understandable system.
tracingmetricsalertingstructured logs
04
Complexity Is a Liability
The best architecture is the one you can explain.
Microservices, event sourcing, and CQRS are tools, not destinations. Each layer of abstraction must earn its place. A well-reasoned monolith beats a poorly understood service mesh every time.
KISSYAGNImodularityboundaries
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
productionRetrieval-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
productionMulti-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
experimentalOn-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
productionDesigning .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 user query to grounded LLM 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
$ rabbitmqctl list_queues name messages consumers
order.stock.reserve 0 2
order.payment.process 1 1
order.sap.sync 0 1
order.deadletter 0 0
$ dotnet-counters monitor --counters commerce.order
Orders Processed/sec 127
Retry Rate (%) 0.3
Dead-letter Queue 0
Avg Processing (ms) 43
$ rabbitmqctl list_consumers --formatter=compact
order.stock.reserve stock-api active
order.payment.process payment-api active
order.sap.sync sap-conn active
$ _
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 — ozberk@systems
Welcome. Type help to see available commands.
$ help
Available commands:contact— Email addressgithub— GitHub profilelinkedin— LinkedIn profilestatus— Current availabilityclear— Clear terminal
M. Özberk Esentürk2026 — Built with Next.js