BACKEND
Full-Stack Software EngineerCasablanca, MABackend-leaning

AnassAbdelhamidHouari.

I build the unglamorous machinerythat refuses to fall over at 2 a.m. — payment rails, order-lifecycle engines, real-time presence, and the occasional memory-leak exorcism.

Scroll
01 / 04
How I think · 01

I treat the boring path as a feature. Idempotency guards, audit logs, and graceful fallbacks are where the real engineering lives.

How I think · 02

If it isn't observable, it isn't done. You can't fix the leak you can't see — so I instrument first and guess never.

How I think · 03

Distributed systems are just trust problems in disguise. Outbox patterns and leader election keep everyone honest across replicas.

How I think · 04

I learned the stack from the socket up — wrote an HTTP server in C++ before I ever trusted a framework to do it for me.

§ 02 — Selected Work

Things I
shipped that
stayed up.

Scroll to travel sideways
01
Ora Technologies· Software Engineer · 2023–Now

Kooul.

A food-delivery SaaS that survives the Friday dinner rush.

Architected the order-lifecycle engine across six modules — pricing, a race-condition-safe idempotency guard, SLA enforcement, delivery-fee computation with location fallback, and an audit log on every state transition. Then built the payment infrastructure from scratch: 3DS, tokenization, saved-card flows with webhook fallback, and an hourly sweep for stuck settlements.

0
Modules in the order engine
0
Heap memory reclaimed across 5 leaks
0
External services integrated
NestJSPostgreSQLKafkaRedisBullMQElasticsearchWebSocketFlutter
02
Open Source· Solo build

Argus.

An audit sidecar that watches your database without touching it.

A self-hosted Postgres audit sidecar that taps the WAL via logical replication, buffers events in Kafka with at-least-once delivery, then fans out to pluggable sinks — Postgres, external DB, HMAC webhook, S3/MinIO. Zero impact on the source DB: no triggers, no writes. A React 19 SPA live-tails the stream over SSE.

0
Triggers on the source database
0
Pluggable event sinks
0
At-least-once delivery, offset-on-ack
NestJSKafkaPrismaReact 19SSE@xyflow
github.com/shinraxtensei/Argus →
03
Real-time· Full-stack game platform

Pong, rebuilt.

Matchmaking, live chat, and a physics engine that doesn't lag.

A multiplayer ping-pong platform with matchmaking, live chat, dynamic ranking and a Matter.js physics core. The React + Redux client keeps state in sync over WebSocket while a NestJS backend juggles concurrent game sessions and authoritative real-time state.

0
Authoritative physics tick
0
Players per live session
NestJSReactReduxWebSocketMatter.jsPostgreSQL
04
Systems· 1337 / 42 Network

A web server, from zero.

Nginx-inspired, hand-written, no HTTP libraries allowed.

A non-blocking HTTP server in C++ built from scratch — I/O multiplexing with epoll / poll / select, a custom HTTP parser, MIME handling, and raw socket I/O. Zero external HTTP libraries. This is the project that taught me what every framework is quietly doing on my behalf.

0
External HTTP libraries used
0
I/O multiplexing backends
C++epollpollselectsockets

“…and a dozen more that
never made the highlight reel.”

03
Field Notes

Things I wish someone had told me sooner.

No. 01The day a logging config ate half my heapObservabilityNo. 02Transactional outbox, or: how I stopped losing eventsDistributed SystemsNo. 03Leader election for people who only have one jobArchitectureNo. 04Building presence in Redis without the Redis adapterReal-timeNo. 05What writing an HTTP server taught me about frameworksSystems
All field notes →
§ 04 — Say Hello

Let's build
something that stays up.

Emailanasshouarii@gmail.com↗GitHub@shinraxtensei↗LinkedInin/anasshouari↗
© 2026 Anass Abdelhamid HouariCasablanca, Morocco · +212 681-650480Built in ink & monospace