{ }
BarScarf
Elegant and reliable e-commerce platform for scarf collections.
BarScarf is a full-featured e-commerce platform dedicated to modern and premium scarf collections. Visitors can discover patterned, plain, silk, cotton, and everyday scarves using pattern, color, and fabric filters. High-resolution product images and color options make the shopping experience both enjoyable and practical. The platform uses a React + Redux Toolkit frontend and a Node.js + Express.js backend with MySQL managed through Sequelize ORM. It includes user registration, login, profile management, and a complete password reset flow. Full shopping features cover cart, favorites, and order management. Product reviews and ratings, iyzico payment integration, and Nodemailer-powered email notifications are all supported. Cloudinary handles image storage and CDN delivery, while Redis provides caching. API security is enforced through Helmet.js security headers, CORS configuration, and request rate limiting. The admin panel covers product, category, user, and order management along with sales statistics. The project is containerized with Docker and deployed on Railway and Render.
Technologies Used
teknolojiler.tsx
<div class="project-info">
<p>
This project was developed using the best tools modern web technologies offer. Each technology was carefully selected to maximize performance, security, and user experience. During development, the focus was on component-based architecture, reusable code, and optimized rendering performance.
</p>
<p>
The user interface was designed to provide a clean yet impactful visual experience. The design system is built on principles of consistency, readability, and accessibility. Modern CSS frameworks and utility tools were used to provide a strong styling foundation.
</p>
<p>
On the frontend, powerful technologies like React and Next.js provided great advantages in terms of fast load times and SEO optimization. Additionally, Tailwind CSS accelerated the design process and made development more flexible.
</p>
<p>
As a result, this technology stack forms a modern and sustainable infrastructure that supports not only today’s needs but also future scalability goals.
</p>
<p>
The project also delivers a seamless experience across all devices thanks to responsive design and a mobile-first approach. Every aspect of the design was optimized for usability and accessibility, ensuring smooth user interactions.
</p>
<p>
Performance optimizations were implemented to minimize page load times, including efficient media and image handling. This approach improves user experience while providing a solid foundation for SEO and overall site performance._
</p>
</div>
JavaScript
Language
React
Frontend
Redux Toolkit
Frontend
HTML5
Frontend
CSS
Frontend
Express
Backend
Node.js
Backend
MySQL
Database
Sequelize
Database
Docker
DevOps
Vercel
DevOps
Railway
DevOps
Render
DevOps
Problem
A scarf retailer needed a complete storefront (search/filter, cart, favorites, reviews) with production-grade security (rate limiting, CORS, security headers) on a budget-friendly, container-deployable stack.
Solution
I built a React + Redux Toolkit frontend against a Node.js/Express + MySQL/Sequelize backend, with Helmet.js security headers, CORS configuration, and rate limiting protecting the API, Redis caching, and Cloudinary for image/CDN — containerized with Docker and deployed to Railway/Render.
Challenges
- Keeping Redux Toolkit cart/favorites state in sync with server-side order/review data without over-fetching.
- Hardening a Node/Express API (rate limiting, CORS, security headers) to a standard suitable for public deployment on a constrained budget stack.
Results
- Shipped a fully containerized, cheaply-hostable e-commerce stack (Railway/Render) without sacrificing security headers or rate limiting.
- Product reviews/ratings and Nodemailer notifications closed the loop on post-purchase engagement.
Lessons Learned
Security middleware (Helmet, CORS, rate limiting) is cheap to add and easy to forget — baking it into the initial Express scaffold, rather than adding it right before launch, turned it into a non-event.
Let's talk about the engineering behind this
If you'd like to discuss the architecture decisions, the tech stack, or a similar technical problem, I'm happy to talk.
Get in Touch