APIs & microservices
REST APIs and service boundaries designed so teams can work in parallel and deploy independently. Clean Architecture and CQRS where they earn their keep — not as decoration.
I'm Hassan Houry. For over a decade I've built production .NET systems — real-time stock trading, wealth management, ERP accounting and high-throughput ETL pipelines — in C#, .NET Core, microservices and CQRS. Not tutorials. Systems people move money through.
The .NET work businesses actually need — not framework tourism. Each of these is something I have shipped and then maintained in production.
REST APIs and service boundaries designed so teams can work in parallel and deploy independently. Clean Architecture and CQRS where they earn their keep — not as decoration.
Live market data, trading flows and portfolio calculations where correctness is not negotiable and latency is visible to the user. Built and run for fintech clients.
Data pipelines, queue-driven workers and scheduled jobs that move large volumes reliably, retry sensibly, and tell you when something breaks instead of failing silently.
Accounting, inventory, insurance and admin systems — the unglamorous software a company runs on daily, where an edge case is somebody's payroll.
Inherited an ASP.NET or WPF system nobody wants to touch? I take those over, make them safe to change, and modernise incrementally instead of betting the business on a rewrite.
Schema design, query tuning and the N+1 hunts that turn an eight-second report into a fast one. PostgreSQL and SQL Server, with the profiling to prove the difference.
React, Angular and TypeScript on the frontend, Flutter and React Native for mobile, plus hosting and CI/CD. Hire one senior engineer instead of assembling a team around a backend contractor.
Every one of these went to production and carried real business traffic.
I'll tell you which one fits your project — including when the answer is that you don't need me yet.
A defined deliverable: an API, a migration, a module, an integration. You know the cost before we start. Best when the requirements are already clear.
Monthly capacity for continuing development, features and maintenance. Best when the product is alive and the roadmap keeps moving.
A senior second opinion: architecture review, code audit, hiring support or a plan for a system that has become hard to change. Short, focused engagements.
Anything not covered here — just ask. I reply personally, usually within a day.
Over 10 years, continuously since 2015 — from ASP.NET and WPF desktop accounting software through to modern .NET Core microservices. I currently lead backend and ETL development, set architecture standards and mentor other developers.
Yes. A large part of my work is joining systems already in production — reading the code, finding what actually hurts, and improving it incrementally without a risky rewrite. I have taken over legacy ASP.NET and WPF systems as well as modern .NET Core services.
Yes. I am full-stack: React, Angular and TypeScript on the frontend, PostgreSQL and SQL Server for data, plus deployment and hosting. You do not need to hire separately for the layers around the .NET backend.
Both. Ongoing retainer or monthly contract for continuing product work; fixed-price for well-defined scopes such as an API, a migration or a specific module. I will tell you which fits your project rather than pushing whichever pays more.
I'm based in Lebanon (GMT+2/+3), which overlaps the full European working day and most of the Gulf and UK. I have worked with teams in Saudi Arabia and remotely worldwide — time zone has never been a blocker.
Tell me what you're building or what's currently breaking. The first conversation is free — and you'll leave it with a clearer plan either way.