Skip to content
View berat-erkul's full-sized avatar
🎯
Focusing
🎯
Focusing

Block or report berat-erkul

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
berat-erkul/README.md
Typing SVG


👋 About Me

I'm a Junior Java Backend Developer from Kocaeli, Türkiye — Software Engineering student at Fırat University, with an Erasmus+ exchange semester at Univerza v Mariboru, Slovenia 🇸🇮. I build backend systems with Spring Boot, break monoliths into microservices, and ship them with Docker + AWS + CI/CD.

I learn by rebuilding — every pattern in this profile started life as a project I tore down and reassembled just to understand why it exists.

public class BeratErkul implements BackendDeveloper {

    private final String[] stack   = {"Java", "Spring Boot", "PostgreSQL", "Docker", "AWS"};
    private final String   focus   = "Migrating monoliths → microservices, one bounded context at a time";
    private       boolean  coffee  = true;

    @Override
    public void philosophy() {
        while (coffee) {
            write(cleanCode());
            test(everything());
            refactor(fearlessly());
        }
    }
}

🧭 The Architecture Journey I'm On

For most of my hands-on work so far I've lived in classic 3-layer / layered architecture — Controller → Service → Repository, simple and effective. Right now I'm deliberately climbing out of that comfort zone for the first time, so consider this diagram a live status, not a finished résumé:

flowchart LR
    A["🧱 Layered Architecture<br/>(what I know well)"] -->|now learning| B["⬡ Hexagonal<br/>Ports & Adapters"]
    B --> C["🏛️ Clean Architecture"]
    C --> D["🧩 Domain-Driven Design"]
    D --> E["🔄 CQRS + Event-Driven<br/>+ Outbox Pattern"]

    style A fill:#2C5364,stroke:#0F2027,color:#fff
    style B fill:#203A43,stroke:#0F2027,color:#fff
    style C fill:#203A43,stroke:#0F2027,color:#fff
    style D fill:#203A43,stroke:#0F2027,color:#fff
    style E fill:#0F2027,stroke:#0F2027,color:#fff
Loading

🙋 Honest note: DDD, Clean and Hexagonal Architecture are brand new to me — I'm seeing them for the first time beyond theory. If you've walked this road, I'd genuinely love a code review or a pointer.


🛠️ Tech Stack



Keycloak JWT OAuth2 Vault CircleCI Prometheus Grafana Zipkin Swagger


🚀 Featured Work

🎫 Ticketing System — v1

Layered Monolith

The same product, rebuilt twice on purpose — this is the "before".

  • Controller–Service–Repository layers
  • Keycloak + Spring Security auth, password hashing
  • AOP performance monitoring, global exception handling
  • Dockerized → AWS EC2 + RDS
  • CircleCI → AWS ECR pipeline

ticketing-project-data →

⚙️ TicketinApp — v2

Microservices Rewrite

User / Project / Task services + Gateway + Eureka + Config Server — the "after".

  • Netflix Eureka service discovery
  • Spring Cloud Gateway + OpenFeign
  • Centralized config + client-side load balancing
  • Distributed tracing: Zipkin, Prometheus, Grafana
  • Independent database per service

TicketinApp →

flowchart TB
    subgraph Client
        U[User]
    end
    U --> GW["🚪 API Gateway<br/>Spring Cloud Gateway"]
    GW --> EU["🧭 Eureka<br/>Discovery Server"]
    GW --> US["👤 User Service"]
    GW --> PS["📁 Project Service"]
    GW --> TS["✅ Task Service"]
    US -.OpenFeign.-> PS
    PS -.OpenFeign.-> TS
    US --> UDB[(User DB)]
    PS --> PDB[(Project DB)]
    TS --> TDB[(Task DB)]
    US --> OBS["📈 Zipkin / Prometheus / Grafana"]
    PS --> OBS
    TS --> OBS

    style GW fill:#2C5364,stroke:#0F2027,color:#fff
    style EU fill:#203A43,stroke:#0F2027,color:#fff
    style OBS fill:#0F2027,stroke:#0F2027,color:#fff
Loading

📊 GitHub Stats

🏆 Trophy Case (click to expand)

🎓 Background

timeline
    title Path so far
    2022 : Started B.Sc. Software Engineering — Fırat University
    2023 : OOP & Java certifications (Inspimo, Cambly)
    2024 : Spring Boot & Java bootcamps (Udemy, CYDEO)
    2025 : Erasmus+ exchange — Univerza v Mariboru, Slovenia
         : Spring Boot Backend Developer — Prodrom ICT Solutions
    2026 : Backend Intern (ASP.NET Core / C#) — TRTEK Yazılım
Loading
  • 📜 Certified: CYDEO Backend/Spring Boot Developer Program, plus Udemy courses in Spring Boot, Java, C++ and Relational DB Design
  • 🌍 English — B2 Professional Working Proficiency

🎸 Off the Keyboard

Guitar, singing, and an unreasonable amount of curiosity about why things break in production.

Let's connect — especially if you know DDD, Clean or Hexagonal Architecture and have opinions.

Pinned Loading

  1. food-ordering-system food-ordering-system Public

    Event-driven food ordering microservices with Clean/Hexagonal Architecture, DDD, SAGA, Outbox and Kafka (KRaft, Avro).

    Java 1

  2. discovery-service discovery-service Public

    Java

  3. gateway-edge-server gateway-edge-server Public

    Java

  4. project-service-microservice project-service-microservice Public

    Java

  5. task-service-microservice task-service-microservice Public

    Java

  6. user-service-microservice user-service-microservice Public

    Java