Backend Software Engineer based in Malaysia 🇲🇾, building reliable Laravel systems — with a focus on clean architecture, domain-driven design, and software that remains maintainable as it grows.
🚀 Open to opportunities: I'm open to backend engineering roles, freelance opportunities, and contributing to interesting open-source projects. If you're building something meaningful and looking for a contributor or engineer, feel free to reach out.
I maintain a small set of focused, single-purpose Laravel packages rather than one large toolkit. Each package is designed to solve a specific problem well and is backed by an automated quality pipeline using PestPHP, PHPStan, Rector, and Laravel Pint.
| Package | Description |
|---|---|
| laravel-trace | Application-level tracing — request, query, and event-level spans for understanding what an application actually did during a request. |
| laravel-idempotency | Prevents duplicate request execution via idempotency keys: request fingerprinting, response replay, conflict detection, and cache-based locking — useful for payments, orders, and external API calls where a retry must not cause duplicate execution. |
A multi-tenant Laravel SaaS platform for academic workflows, student records, and administrative operations, with domain isolation and role-based access control.
Madarik is a commercial product used by schools, so its source code is private. The live deployment provides the best way to explore the system.
Demo credentials (click to expand)
| Role | |
|---|---|
| Developer | developer@madarik.test |
| Principal | principal@madarik.test |
| Admin | admin@madarik.test |
| Parent | parent@madarik.test |
Password (all roles): o/\Efy1vP0k?aOgM
- Backend workflows for student management, grading, and reporting
- Role-based access control across distinct user groups
- Redis-backed background processing
- Dashboards built with Laravel, Vue.js, and Inertia.js
- Multi-tenant architecture with isolated application contexts
A Laravel application designed around domain-driven design and complex, multi-tenant business workflows.
- Business logic structured around clear domains, value objects, domain events, and isolated business rules
- Multi-tenant architecture with automated tenant scoping
- Event-driven workflows between application modules
- Administrative interfaces built with Filament
- Focus on maintainability, separation of concerns, and scalable business logic
I'm particularly interested in backend engineering problems where correctness and maintainability matter:
- Domain-Driven Design
- Multi-Tenant Architecture
- Distributed Systems
- Idempotency & Reliable Request Processing
- Event-Driven Architecture
- Background Jobs & Queues
- Observability & Application Tracing
- API Design
- Automated Testing
- Code Quality & Static Analysis
- Laravel Ecosystem & Package Development
I maintain projects across two GitHub accounts:
- Primary: github.com/AdilAzhari
- Additional: github.com/AdilAzhariOmsan
For the most recent backend engineering work, packages, and projects, start with my primary account.
