About

About

Hi, I’m Alparslan — a freelance .NET developer with a few years of hands-on experience building backend systems in C# and ASP.NET Core. I like working close to the data layer: APIs, middleware, and the caching decisions (Redis, in-memory, distributed) that decide whether an application stays fast under real traffic.

Most of what I write about here comes directly from things I’ve built or run into at work — middleware I’ve published as NuGet packages, caching patterns I’ve had to explain to teammates, error-handling approaches I settled on after trying the messier alternatives first.

What I Do

  • Backend APIs — ASP.NET Core Web APIs, middleware pipelines, request/response logging, global exception handling.
  • Data & caching — Entity Framework Core, Redis, in-memory and distributed caching strategies.
  • Practical engineering — rate limiting, containerization (Docker, .NET’s built-in container support), and writing code that’s boring to debug at 2 AM.

Skills

Languages & Frameworks C#, .NET 8/9, ASP.NET Core, Blazor, Angular

Data & Caching MSSQL, PostgreSQL, MongoDB, Redis, Elasticsearch

Architecture & Practices REST API design, Microservices, CQRS, Clean/Onion Architecture, DDD, SOLID

Tools Docker, Git, Azure DevOps, Visual Studio / VS Code

Open Source

I’ve published a couple of small NuGet packages that grew out of patterns I kept rewriting on projects:

  • CD.RequestResponse.Middleware — structured HTTP request/response logging for ASP.NET Core.
  • CD.File-Logger.Middleware — a file-logging extension for the package above.

Source for both lives in request-response-nuget-package on GitHub.

This Blog

I write about the .NET and ASP.NET Core problems I actually run into — mostly caching (there’s a small Redis series here), middleware, and error handling. No filler, no “10 tips” listicles — just what I’d want to read if I were debugging the same thing at 11 PM.

Beyond Code

Outside of work I’m into films, books, and games — the usual developer diet. If you want to talk about any of that instead of caching strategies, I won’t complain.


GitHub · LinkedIn · Email