fsFurkan ŞahinSoftware Engineer
GitHub

backend / istanbul

Furkan Şahin

Software Engineer

I build backend systems for high-volume messaging platforms: REST and SOAP APIs, RabbitMQ-driven services, and the SQL and caching layers behind them. Outside work, I run a self-hosted homelab end to end.

View ResumeGitHub

experience

Backend in production

Three years on messaging platforms that send at volume: APIs, queues, data, and the pipelines that ship them.

  1. Software Engineer · Biotekno

    Jun 2023 - Present

    • High-throughput SMS APIs (REST, SOAP) on .NET Core in production, with real-time updates via SignalR.
    • Multiple integrated products with dedicated databases, talking asynchronously over RabbitMQ and synchronously over HTTP.
    • Custom identity and authorization service with role- and permission-based access control.
    • Query and stored procedure tuning across MySQL, PostgreSQL, and MSSQL, plus distributed caching with Redis and Apache Ignite.
    • CI/CD with Jenkins and Docker, containerized deployments on Linux servers.
    .NET CoreRabbitMQSignalRRedisApache IgniteJenkinsDocker

  2. Software Developer Intern · Bilgeadam Technology

    Feb 2023 - Apr 2023

    • Online examination system with ASP.NET Core MVC in an Agile/Scrum team.
    ASP.NET Core MVC

  3. Before software

    Structural and site engineering (2019 - 2022). Moved into software in 2023.

stack

Backend-heavy, infrastructure-aware

The stack is intentionally practical: APIs, async workloads, relational data, containers, and the patterns needed to keep services maintainable.

Backend

C#.NET CoreASP.NET CoreEntity Framework CorexUnitGo (basic)

Architecture

MicroservicesEvent-drivenCQRSMediatRSOLIDRESTSOAP

Messaging / Async

RabbitMQSignalRHangfire

Data

PostgreSQLMySQLMSSQLRedisApache Ignite

DevOps / Infra

DockerDocker ComposeLinuxNginxCaddyCloudflareJenkinsGitHub Actions

AI & Automation

n8nOllamaCoding agents

daily drivers in production

projects

Featured work

Small public tools and the platform they run on, built, containerized, deployed, and operated end to end.

Homelab Platform

Live

Oracle Cloud VPS and a home Linux server behind Cloudflare and Caddy. Apps ship as Docker images built by GitHub Actions and published to GHCR.

DockerCaddyCloudflare TunnelGitHub ActionsOllama
See the setup

homelab

Two hosts, one delivery flow

Public tools live on an always-on cloud VPS. Heavier workloads like local LLMs run on a home server behind Cloudflare Tunnel. Everything ships as a container image.

Cloud edge

Oracle Cloud VPS

Always-on public side for small tools and this site.

  1. internet
  2. Cloudflare DNS
  3. Caddy
  4. Docker

Home server

Dell G3, Linux

Heavier workloads at home, no open ports.

  1. internet
  2. Cloudflare Tunnel
  3. Docker
  • OllamaSelf-hosted LLM runtime
  • Open WebUIChat UI for local models
  • DeepWikiAI-generated code docs

delivery

  1. git tag v*
  2. GitHub Actions
  3. GHCR image
  4. docker compose pull

next

k3s on the home server

connect

Get in touch

Open to conversations about backend engineering, distributed systems, and platform work. The resume has the full picture.

Download ResumeLinkedInEmail