About the service
I'm a backend developer on the dotnet platform and C# language, and I design server systems you can actually rely on. The bulk of my work is web API on ASP NET Core: neat REST or gRPC endpoints, correct authentication and authorization, validation, structured logging and versioning. Everything is assembled so the contract stays stable and the implementation can evolve calmly. I think in layers and boundaries, not a pile of controllers, so the code stays readable months after release, and new features are integrated without breaking what already works.
On the data side, I rely on Entity Framework Core, but never treat it as a black box. I write efficient queries, watch for the N+1 problem, carefully prepare migrations and when necessary, drop down to raw SQL or stored procedures when the query planner needs a firm hand. When one service becomes insufficient, I split responsibility into microservices that communicate through message queues or a well-designed gateway, add caching where it's justified and watch latency and throughput by actual metrics, not guesswork. Background tasks, schedulers and long-lived processes are part of the same discipline.
Integrations are an important part of what I do: payment providers, CRM, storage, email and external APIs wrapped in resilient clients with retries, timeouts and circuit breaker so one unstable dependency doesn't bring down the whole system. I write unit and integration tests, package services in containers and hand over documentation your team can work with. Whether you have a new project from scratch or an aging codebase that needs modernization, I'll take it from architecture to deployed service under monitoring.
— Web API on ASP NET Core (REST and gRPC)
— Entity Framework Core, SQL optimization and migrations
— Microservices, message queues and API gateways
— Authentication, authorization and JWT security
— Integrations with payment and external services, resilient clients
— Unit and integration tests, Docker, CI
On the data side, I rely on Entity Framework Core, but never treat it as a black box. I write efficient queries, watch for the N+1 problem, carefully prepare migrations and when necessary, drop down to raw SQL or stored procedures when the query planner needs a firm hand. When one service becomes insufficient, I split responsibility into microservices that communicate through message queues or a well-designed gateway, add caching where it's justified and watch latency and throughput by actual metrics, not guesswork. Background tasks, schedulers and long-lived processes are part of the same discipline.
Integrations are an important part of what I do: payment providers, CRM, storage, email and external APIs wrapped in resilient clients with retries, timeouts and circuit breaker so one unstable dependency doesn't bring down the whole system. I write unit and integration tests, package services in containers and hand over documentation your team can work with. Whether you have a new project from scratch or an aging codebase that needs modernization, I'll take it from architecture to deployed service under monitoring.
— Web API on ASP NET Core (REST and gRPC)
— Entity Framework Core, SQL optimization and migrations
— Microservices, message queues and API gateways
— Authentication, authorization and JWT security
— Integrations with payment and external services, resilient clients
— Unit and integration tests, Docker, CI
