emirhan

Hello, I’m

Emirhan Ünsal.

Backend-focused software engineer building reliable systems in the cloud.

I work with Java, Spring Boot, and AWS to build APIs, integrations, and cloud infrastructure. This is where I share my projects and what I learn along the way.

Istanbul, Türkiye Backend & cloud engineering

about me

I’m a backend-focused software engineer interested in reliable APIs, distributed systems, integration workflows, and cloud architecture.

I love working with AWS and exploring how cloud services come together to create scalable, reliable systems. I’m especially interested in backend architecture, distributed systems, integrations, and automating the path from code to production.

what I’m focused on

LAST UPDATED · SEPTEMBER 2026

  • 01

    Production-ready backend systems

    Building services with Java and Spring Boot that remain understandable as they grow. I’m focusing on clear API boundaries, validation, authentication and authorization, persistence, testing, predictable error handling, and containerized delivery—not just making an endpoint work.

    • Java
    • Spring Boot
    • REST
    • PostgreSQL
    • Docker
    • CI/CD
  • 02

    AWS architecture & SAA-C03

    Working through the architecture patterns covered by the AWS Certified Solutions Architect – Associate track: secure multi-tier networks, highly available compute, appropriate data stores, event-driven workloads, disaster recovery, observability, and cost-aware design.

    Compute & containers
    EC2, Auto Scaling, ELB, Lambda, ECS, ECR
    Networking & delivery
    VPC, Route 53, CloudFront, API Gateway
    Data & storage
    S3, EBS, EFS, RDS, Aurora, DynamoDB, ElastiCache
    Security & operations
    IAM, KMS, Secrets Manager, WAF, CloudWatch, Config
    Application integration
    SQS, SNS
  • 03

    Distributed systems & integrations

    Exploring the trade-offs behind asynchronous communication and service-to-service integration: queues, caching, retries, idempotency, dead-letter handling, eventual consistency, and failure recovery. I apply these ideas with RabbitMQ, Redis, Apache Camel, REST, and SOAP.

    • RabbitMQ
    • Redis
    • Apache Camel
    • REST
    • SOAP
  • 04

    Delivery, reliability & observability

    Improving the full path from commit to production with repeatable builds, automated deployments, health checks, safe rollbacks, structured logging, metrics, and actionable alerts. The goal is to build systems that are straightforward to operate when something goes wrong.

    • GitHub Actions
    • Docker
    • Nginx
    • CloudWatch
    • Sentry

selected projects

View GitHub
01

Deployment Control Center

A deployment control panel that connects to remote Linux servers over SSH, deploys Docker images, runs health checks, and automatically rolls back failed deployments.

  • Java
  • Spring Boot
  • PostgreSQL
  • Docker
  • AWS
02

AWS Minecraft Server Panel

An authenticated web panel for starting, stopping, and checking an EC2-hosted Minecraft server while keeping idle infrastructure costs low.

  • EC2
  • Lambda
  • IAM
  • CloudWatch
  • Spring Boot
03

Distributed Calculator

A distributed calculation system where a REST API routes requests through RabbitMQ to independent worker services, with Redis caching for repeated computations.

  • Java
  • Spring Boot
  • RabbitMQ
  • Redis
  • Docker
04

Serverless Blog Platform

A serverless blog platform with a static S3 frontend and a Lambda REST API for storing and retrieving content from DynamoDB.

  • Lambda
  • API Gateway
  • DynamoDB
  • S3
  • Python

recent notes

Why Singleton Does Not Mean Thread-Safe

Why a singleton Spring Bean can still have race conditions, and how stateless design or atomic operations can make concurrent access safer.

3 min

Have something in mind?

Let’s build something reliable.

I’m always happy to talk about backend systems, cloud projects, or a new opportunity.