Architecture close to implementation
I am Fatih Mehmet Arslan, a software engineer who stays involved from technical decisions through implementation and production troubleshooting. My work spans public-sector systems, energy telemetry, retail, SaaS and regulated integrations.
For me, architecture starts with the constraints of the system: who owns the data, which failures must be contained, and what the team can operate. Choosing microservices is a consequence of those decisions, not a starting requirement.
Boundaries, regulation and operational trade-offs
When a platform grows, splitting a service can reduce coupling but also introduce network failures and consistency problems. In regulated systems, data location and audit requirements also influence where a boundary belongs. The following articles explain the reasoning behind these decisions:
- How I decide whether to split or merge services
- Sovereign cell architecture and regulation-oriented design
Related experience
Continue with distributed systems and Peppol integration, or read my professional experience and how I work.