Software Engineer · Hands-on architecture
Hi, I am Fatih. For more than 14 years, I have built software for public services, energy, retail, SaaS, and regulated document exchange. I make architecture decisions close to the code, the data, and the problems that appear in production.
tools.tarsolution.com
A toolbox I built for practical needs in software development, data integration and industrial automation. It brings together utilities for JSON formatting and validation, data format conversion, JWT inspection, Modbus analysis and XML/XSLT transformation.
Explore the tools ↗What I work on
A technology choice is not a result by itself. Clear boundaries, data ownership, failure behaviour, and the team's ability to operate the system matter just as much as the tools we choose.
I make service boundaries, data ownership, and failure paths explicit in systems built with Kafka, asynchronous processing, and multi-tenant services.
Backend and integration
In Peppol and document flows, I work on delivery together with validation, audit trails, data location, and tenant isolation.
Peppol and compliance
I measure the bottleneck before splitting a monolith. At Mantis, this approach helped one platform grow from about 300 to more than 20,000 concurrent users.
SaaS and cloud
I treat code review, observability, and troubleshooting as part of architecture. The value of a decision becomes clear under real traffic and real failures.
Delivery and operations
Examples from my work
I have worked across different industries and technology stacks. The common task has always been to make system boundaries and failure modes visible.
I build multi-tenant services that validate, transform, and route documents from ERP and SaaS products to European delivery networks.
We separated large enterprise applications into modular SaaS and FaaS components, while scaling one platform beyond 20,000 concurrent users.
I built store-and-forward services that protected data during connection loss at remote plants, together with high-volume telemetry pipelines.
Latest writing
I write about why a decision was made, where it failed, and what it cost in production, using concrete examples whenever possible.
A cohesive development experience and one on-premises installation package for a distributed application: boundaries,...
Read article →How I turned AI from a chatbot into an operational layer using skills, documentation, independent review, explicit pe...
Read article →Microservices cannot eliminate dependencies. The practical goal is to contain how changes, latency, and failures prop...
Read article →How a data pipeline becomes a flow, where ready-made tools remain useful, and when a dynamic flow engine becomes a re...
Read article →Kubernetes, Helm, Kustomize, and GitOps manage different layers of delivery. I explain what each one solves and how t...
Read article →The benefits and limits of enums, strings, registries, and contracts for managing domain codes in microservice and Fa...
Read article →A reflection article on AI, FlyWire, BrainNet, Neuralink and new generation intelligence systems.
Read article →Sovereign Cell Architecture: A brief technical note outlining the basic approach and actionable steps on Regulation-D...
Read article →If you want to discuss distributed systems, regulated integrations, or a modernisation decision, you can reach me directly by email.