Abdullah Sarwar in a suit

Abdullah Sarwar

Dhaka

1′Kick-off

Two things have held my attention for years: football and software. This page is about both.

The first half is football. The second half is engineering. At half-time, I pick a team.

1′ – 45′First halfFootball

Abdullah seen from behind on a floodlit pitch at night, in a No. 7 shirt with his name, holding a trophy and his boots
No. 7, under the floodlights.

Away from the keyboard, my life is about three things: family, friends and football.

THE THEATRE OF DREAMS

45′Half-timeThe team sheet

Football shapes how I think about software too. I see my tools as a team, and this is the side I would pick.

Grafana MongoDB Postgres MySQL Redis RabbitMQ Loki Raw SQL Cron jobs AI agents NestJS

Tap a player to see why it is in the side.

Manager

Abdullah Sarwar

Home ground

Node.js

Away ground

Python

Formation

Substitutes
Tap one to bring it on

4-4-1-1: data at the back, the plumbing in midfield, NestJS up front. AI agents (Claude Code, Codex, T3 Code) play false 9: they drop deep and set up the finish. The manager picks the team and owns the result.

How I work with AI agents

46′ – 90′Second halfSoftware

I lead the Public API team at ShareTrip. When something goes wrong, I go to the evidence first: query plans, logs and traces, until the real cause is clear.

I like raw SQL more than ORMs. I want to know exactly what the database is asked to do.

Abdullah at his desk at ShareTrip, turned toward the camera, with three monitors behind him
At my desk at ShareTrip.

Most of the work ends the same way: someone books a trip, and it just works.

Stamped and readyThe passport opens, the stamp lands, and the boarding pass slides into place.
Abdullah with ShareTrip's CEO in the office

I write these problems up when I can.

Fixtures and resultsStatus

  1. Following One Request Through Logs with Grafana and LokiResult
  2. Query Profiling Found More Than Slow QueriesResult
  3. Designing RabbitMQ Routing for Multiple MarketsResult
  4. Making Booking Retries SafeResult
  5. Speeding Up Hotel Search with Concurrent ChunksResult
  6. Upgrading Node in a Service That Renders PDFsFixture
  7. Building Safer Production Access for AI Coding AgentsFixture
  8. One Booking Code Across Several ServicesFixture

Planned titles can change.

90+3′Full timeHonours and contact

  • Abdullah Sarwar holding the Champion board at the Banglalink SDG Hackathon: Code for a Cause 2.0

    Hackathon

    Champion, Banglalink SDG Hackathon: Code for a Cause 2.0

    Thirty-six hours, one team, Team QuirkyBits. It is the closest software gets to a cup final.

That is both halves. For the full record of my work,

abdullah.md.sarwar@gmail.com

Abdullah

About

I'm a senior software engineer in Dhaka. I lead the Public API team at ShareTrip and work on the backend behind its bookings, payments and pricing.

In my work, search must be fast and efficient. Every level of markup and discount must match. Every booking and payment must be traceable.

I write about the design choices behind that work, and what each one cost.

Abdullah at his desk at ShareTrip, turned toward the camera, with three monitors behind him
At my desk at ShareTrip.

What my team builds and maintains

  • Gateways
  • Flights
  • Hotels
  • Visa
  • Holidays
  • Shop
  • Recharge
  • Bill pay
  • B2B
  • B2E

Selected work

ShareTrip · Public API team

The Public API team

Scope

The team owns the backend for flights, hotels, visa, holidays, e-commerce, mobile recharge and bill payments. It serves consumers, B2B and B2E. Under every product sit the same three problems: , , and .

How we work

. Services talk through RabbitMQ. Before either side is written, we agree where each message goes and when it counts as handled.

. We profile a query before we change it, and .

. One ID follows a request across services, and we read it in Grafana and Loki.

. Every change runs in staging before production.

More about this work

ShareTrip · Bookings

Making booking retries safe

Problem
A booking request can arrive more than once, after a timeout or a repeated tap. A repeat must not take a second room.
The tempting answer
Check whether the booking exists, then create it. Two requests can both finish the check before either one creates the booking.
What we did
We use the booking identifier to recognise repeats. A MySQL named lock orders work on the same booking, and a transaction groups the database changes. Cancellation follows the same rules.
Result
A repeated request returns the existing booking, and inventory changes once.

Read the write-up

ShareTrip · Public gateway

Rate limits that follow the caller

Problem
A public gateway must slow down abusive callers without slowing down everyone else. Many normal users can share one address, and a proxy can hide the real one.
The tempting answer
One shared limit for the whole platform. It is simple, but one busy caller then uses up the allowance of every other caller.
What we did
Each caller gets its own bucket. The caller's address comes only from the forwarded header that the platform's own ingress sets. One wide platform limit stays as a last safety net.
Result
A busy caller now uses up only its own allowance. Every other caller keeps its normal speed.

Experience

Projects

PadelHub BD · Sole developer

A ranking that players can check

A ranking and tournament platform for padel players in Bangladesh. Players submit match results from their phones at the court. An opponent or an admin confirms each result, and confirmed results feed a public ranking. I built it end to end, with Laravel, Filament and MySQL.

Problem
A ranking only works if players trust it. One hidden rule, and they stop submitting results.
The tempting answer
Keep the formula in code and show only the final number. Players cannot check a number they cannot trace, and every rule change becomes a deploy.
What I did
The platform has four parts: the ranking engine, the tournament engine, the admin panel and the public site. I put every ranking constant in one config file, and the tests read that same file. Each player has a breakdown page that shows which results produced the points. The public table is served from precomputed snapshots. Tie-breaks follow one fixed ladder.

padelhubbd.com

  1. Points
  2. Head-to-head only when exactly two teams are tied
  3. Game difference
  4. Games won
  5. Wins

Toolkit

Languages and services

TypeScript on Node.js, with NestJS and Express. PHP with Laravel for PadelHub BD. Python when the task needs it.

PadelHub BD

Data

PostgreSQL, MySQL, MongoDB, Redis and Typesense. Raw SQL first, TypeORM where it helps.

Count the round trips

Messaging

RabbitMQ between services, cron for scheduled jobs. The routing is agreed before the code is written.

Designing RabbitMQ Routing for Multiple Markets

Observability

Grafana and Loki. One ID follows each request.

One ID through four services

AI tools

Claude Code, Codex and T3 Code. A person reviews every change.

How I work with AI agents

Writing

Recognition

  • Abdullah Sarwar holding the Champion board at the Banglalink SDG Hackathon: Code for a Cause 2.0

    Hackathon

    Champion, Banglalink SDG Hackathon: Code for a Cause 2.0

    A 36-hour hackathon, won with Team QuirkyBits.

Research

Before backend work, I published three peer-reviewed papers in natural language processing and data mining, including a question-answering system for Bengali.

Publications and reports

Off the pitch

Abdullah seen from behind on a floodlit pitch at night, in a No. 7 shirt with his name
No. 7, under the floodlights.

Away from work, I play football and support Manchester United.

Contact

Keep scrolling for the next pageKeep scrolling… Abdullah Sarwar Work