Senior Backend Engineer specializing in transaction-safe and high-concurrency backend systems, distributed architectures, and high-traffic production environments.

Backend engineer with 7+ years of commercial experience building and operating transaction-safe, high-concurrency systems in real production environments.

I design backend systems that handle financial integrity, race conditions, distributed workloads, and infrastructure-level scaling — not just APIs.

My focus is on correctness under pressure, system reliability, and clean architectural decision-making.

• Transaction-safe financial systems (idempotent APIs, atomic flows)
• High-concurrency order and payment processing
• Distributed locking & race-condition prevention
• Event-driven architectures (queues, async workers)
• High-traffic REST API design
• Database performance optimization (MySQL / PostgreSQL)
• Infrastructure ownership (AWS, Docker, CI/CD)
• Backend team leadership (7 engineers) & hands-on architectural ownership

• Built and maintained fintech systems handling real monetary transactions
• Designed idempotent payment flows with consistency guarantees
• Optimized high-traffic systems under concurrent load
• Led backend engineers while remaining hands-on in architecture and code
• Owned AWS infrastructure deployment and CI/CD pipelines

• PHP (Laravel)
• Node.js + TypeScript
• RESTful APIs
• Event-driven systems
• Worker-based architectures

• MySQL (query tuning, indexing, transaction management)
• PostgreSQL

• Redis
• Distributed queue processing
• Concurrency control patterns

• AWS (EC2, S3)
• Docker
• CI/CD pipelines
• Production deployment workflows

High-concurrency backend architecture simulating multi-vendor transactional flows with race-condition prevention and event-driven processing.

→ Atomic inventory reservation
→ Queue-based async workers
→ Concurrency-safe design
→ Failure scenario analysis
→ Explicit trade-offs documentation

Repository: https://github.com/AbdouShalby/Distributed-Order-Processing-System

Technical exploration of distributed locking strategies, failure cases, and concurrency edge scenarios.

→ Locking mechanisms comparison
→ Race-condition simulations
→ Trade-off analysis
→ Real-world production implications

Repository: https://github.com/AbdouShalby/Distributed-Locking-Deep-Dive-Lab

Deep architectural breakdowns of scalable backend systems including fintech, high-scale marketplaces, real-time notifications, and rate limiting.

Each case study includes:

• Requirements & constraints
• Capacity estimation
• Architectural decisions
• Trade-offs & known risks
• Failure scenarios
• Mitigation strategies

Repository: https://github.com/AbdouShalby/Backend-Architecture-Case-Studies

• Production realism over theoretical design
• Strong ownership mindset
• Clear architectural reasoning
• Reliability-first engineering
• Clean and maintainable system design
• Ability to operate in high-risk, high-growth startup environments

LinkedIn: https://linkedin.com/in/abdelrhman-shalby
Email: abdoushalby@gmail.com