You will get your slow ASP.NET Core API endpoints sped up with Redis caching
Project details
Your ASP.NET Core API works, but some endpoints are slow enough that users notice. Redis caching is usually the cheapest fix - when it is applied to the right endpoints and invalidated correctly.
On my Talabat e-commerce API, adding JWT auth and Redis caching cut response time by 25%. I know where caching genuinely helps and where it just adds a stale-data bug you will hit later.
What you get:
• Your current response times measured first, so there is a real baseline
• Up to 5 endpoints cached with Redis
• Sensible expiry times and correct cache invalidation
• Before and after numbers so you can see the actual gain
• Your updated source code back
I will be honest with you: if your slowness is a missing database index or an N+1 query rather than a caching problem, caching will not fix it. Send me the endpoint and I will tell you which one it is before you order.
On my Talabat e-commerce API, adding JWT auth and Redis caching cut response time by 25%. I know where caching genuinely helps and where it just adds a stale-data bug you will hit later.
What you get:
• Your current response times measured first, so there is a real baseline
• Up to 5 endpoints cached with Redis
• Sensible expiry times and correct cache invalidation
• Before and after numbers so you can see the actual gain
• Your updated source code back
I will be honest with you: if your slowness is a missing database index or an N+1 query rather than a caching problem, caching will not fix it. Send me the endpoint and I will tell you which one it is before you order.
Programming Languages
ASP.NET, C#Coding Expertise
Performance OptimizationWhat's included $150
These options are included with the project scope.
$150
- Delivery Time 3 days
- Number of Revisions 3
- Number of Pages 5
- Source Code
About Abdelrhman
.NET Backend Developer | ASP.NET Core REST APIs & Payment Systems
Cairo, Egypt - 9:09 pm local time
For two years I worked as a Software Developer at the Agricultural Bank of Egypt, building RESTful APIs with ASP.NET Core Web API for wallet transactions, balance inquiries, and payment processing. I implemented CRUD operations for transaction records using Entity Framework Core and SQL Server to keep ledger data accurate, and unit tested and debugged every endpoint before deployment. I also trained 500+ bank employees on the Finacle core banking system, earned a Super User badge, and supported 20+ branches - so I understand banking workflows from both the code side and the operations side.
WHAT I CAN BUILD FOR YOU
- REST APIs with ASP.NET Core Web API - clean, versioned, and documented with Swagger
- Payment, wallet, and transaction processing flows
- JWT authentication and role-based authorization
- SQL Server database design, Entity Framework Core, Dapper, migrations and seeding
- Redis caching and API performance optimization
- Real-time features with SignalR
- Maintainable code using Onion Architecture, SOLID, and design patterns (Repository, Unit of Work, Singleton, Factory, Observer)
- Deployment to IIS, with Git and Azure DevOps CI/CD
SELECTED PROJECTS (full code and details in my portfolio below)
Talabat API - E-Commerce Web API
Secure login, cart, and order management APIs built with ASP.NET Core and SQL Server. Added JWT authentication and Redis caching, which cut API response time by 25%. Built on Onion Architecture and SOLID principles.
Order Management System API
Customer and product management with full CRUD and stock control, JWT role-based access, order processing with automatic stock validation, tiered discounts, and multi-payment support (credit card, PayPal, bank transfer, cash), plus automated invoice generation and email notifications.
TECH STACK
C# | ASP.NET Core | ASP.NET MVC | Web API | Entity Framework Core | Dapper | LINQ | SignalR | SQL Server | Redis | AutoMapper | Swagger | Postman | Git | Azure DevOps | IIS
I also teach backend development to 400+ computer science students as a Teaching Assistant at Lotus University, so I can explain technical decisions in plain language and write code other developers can actually maintain.
I am available 30+ hours per week and reply to messages within a few hours. Tell me what you are building or what is broken, and I will give you an honest assessment of whether I am the right fit.
Steps for completing your project
After purchasing the project, send requirements so Abdelrhman can start the project.
Delivery time starts when Abdelrhman receives requirements from you.
Abdelrhman works on your project following the steps below.
Revisions may occur after the delivery date.
Measure the current response times
I run your endpoints and record how long each one actually takes. Without a baseline there is no honest way to prove the caching worked, so this comes first.
Add Redis caching where it actually helps
I wire Redis into your ASP.NET Core project and cache the endpoints that are genuinely slow, with sensible expiry times and correct invalidation so clients never see stale data.