💻 Junior Computer Engineering Student | Full-Stack Developer & System Architecture Enthusiast
I focus on building end-to-end, scalable, and robust systems—ranging from user interfaces (Frontend/iOS) to background services (Backend) and database management. I don’t just write code; I love designing the "whole system" based on solid engineering principles.
- Currently developing Nexus-A-Full-Stack_AI-Driven-E-Commerce-Architecture, a comprehensive retail ecosystem.
- Expanding my expertise in Polyglot Persistence, Microservices, Modern Web (React/Node), and iOS Development.
- I enjoy discussing System Design, API Architectures, and integrating Data Science (AI/ML) into real-world projects.
Not just another CRUD app; this is an end-to-end system engineering project integrating Frontend, Backend, Cloud Infrastructure, and Data Science modules.
The core of the project relies on a Polyglot Persistence approach, choosing the right tool for the data's specific nature while maintaining a secure infrastructure:
🔍 Architectural & Database Decisions:
- Users (PostgreSQL): Identity and role management are handled in a relational database to ensure strict data integrity (ACID). To prevent enumeration attacks, UUIDs are used instead of sequential IDs.
- Products (MongoDB): A NoSQL (Document-based) architecture was chosen to flexibly store variable metadata (specs, colors, sizes) without creating sparse columns or empty fields.
- Orders (PostgreSQL): Financial transactions are entrusted to a reliable relational structure. To ensure audit trails remain intact, the
unit_pricefield is strictly designed to store a "snapshot of the price at the time of sale," preventing historical records from changing when product prices are updated.
| Category | Technologies |
|---|---|
| Database & Caching | |
| DevOps, Cloud & Architecture | |
| Backend & API (Microservices) | |
| Frontend & Mobile Clients |
LinkedIn |
© 2026 Alime KILINÇ. All Rights Reserved.
The architectural overview, system design details, and documentation written in this repository are the intellectual property of the author. You may not copy, reproduce, or distribute this text in your own profile or projects without explicit permission.