Skip to main content

Senior Software Engineer

Namshi.comJun 2013 - Aug 2018

Five years at Namshi: built its service architecture from scratch, integrated Cybersource and Apple Pay for tens of thousands of daily transactions, and moved to many small releases.

Technologies Used

  • Node.js
  • Docker
  • Kubernetes
  • GKE
  • AWS
  • GCP
  • Angular
  • Solr
  • Redis
  • MySQL
  • Symfony
  • PHP
  • Cybersource
  • Apple Pay

I spent five years at Namshi, from 2013 to 2018. I joined when the platform still ran on its parent company's stack and left after it ran on containers in the cloud. In between I led four projects, one after another.

About Namshi

Namshi is one of the Middle East's biggest online fashion stores. It sells more than 1,300 international and local brands, from Nike, adidas and Tommy Hilfiger to its own in-house lines, across the UAE, Saudi Arabia, Bahrain, Kuwait, Oman and Qatar. Customers get fast free delivery in the GCC, 24-hour delivery in the UAE, 14-day exchanges and cash on delivery.

The four projects

1. Leaving the parent stack (2013-2014)

Namshi was part of Rocket Internet, a sister company of Mizado, and it started on the same Alice & Bob engine. That is where I started too.

Then we moved to our own service-oriented architecture, built from scratch: everything became API calls, with Angular on the frontend. I worked a lot on the search module, on the APIs and on Angular components. I designed customer-facing services (checkout, payment integration, the search index) and internal systems (warehouse inbound and outbound, the CMS).

Over the following years this became cloud-native. We moved to Docker, with Kubernetes for orchestration and Helm charts for deployments, and I worked on that move too.

2. Order processing for customer support (2014-2015)

Support agents jumped between systems to answer "where is my order?". I led a new order processing app that pulled order status and history into the CRM, so agents could answer from one screen.

I also worked on the call center system. When a customer called, Zendesk opened that customer's profile automatically, matched by the phone number on their account.

3. Warehouse and search (2015-2016)

I led the warehouse management app and its integration with the ERP, covering inventory and fulfilment.

Warehouse staff used it on phones, as a mobile app and a mobile web app. They scanned items coming in and going out, which cut the time those operations took. Not every corner of the warehouse had a connection, so the app had to keep working offline. We built it in-house, with no outside vendor.

In the same period I upgraded the Solr full-text search index with zero downtime. Search is how people find clothes on Namshi, so taking it offline was not an option.

4. Payments (2016-2017)

Payment gateways changed more than once. I built the integration with Innovate, and later worked on the migration to Noon Payments. I also integrated the Cybersource payment gateway and Apple Pay, next to cash on delivery. Together they processed tens of thousands of transactions a day across the GCC, and I owned payment reliability end to end.

From weekly releases to many small ones

We used to ship one big release a week. We moved to tens of small releases, so teams could work in parallel without waiting on each other to deploy.

Search and peak traffic

Search got more than the Solr upgrade. We added auto-complete with suggestions as people typed.

Fashion e-commerce has its big days: Black Friday and the seasonal sales. The systems had to take those spikes, which meant Redis caching for hot data and sessions, a CDN in front of the site, database scaling as the data grew, and auto-scaling once services ran on Kubernetes.

The integrations kept growing too: payment providers, the ERP, and regional shipping and logistics companies, all kept in sync with our own data.

The platform underneath

Over those five years the stack moved from PHP and Symfony 2 to Node.js services in Docker, run on Kubernetes (GKE) with parts on AWS.

  • Backend: Node.js, PHP with Symfony 2, REST APIs
  • Frontend: Angular
  • Data and search: MySQL, Redis, Apache Solr
  • Infrastructure: Docker, Kubernetes on GKE, Helm, AWS, Travis CI
  • Monitoring: New Relic, Sematext, hc.io

What I took from it

Five years at one company let me see my own decisions age, from the first migration to the last payment method.

It is also where I went from writing features to leading projects: picking the approach, getting the warehouse and support teams to agree on it, and mentoring the engineers who built it with me.

I owned applications end to end, and I worked side by side with product and directly with stakeholders. A good part of the job was product engineering.

More experience

All experience
  1. May 2023 - Mar 2026

    Staff | Senior Payments Integration Engineer

    Adyen

    Owned Adyen's 11 SDKs and plugins (Magento, Shopware, 7 API libraries) for hundreds of enterprise merchants, May 2023 to March 2026.

    PHPNode.jsPythonDocker+5
    View details
  2. Sep 2018 - Aug 2019

    Microservices Migration

    Helloprint

    Drove Helloprint's move from a PrestaShop monolith to CQRS and event-sourced microservices on Kubernetes, including the payment integration.

    KubernetesKafkaPostgreSQLContentful+6
    View details
  3. Oct 2012 - May 2013

    Web Developer

    AlWasatt Network FZ-LLC

    Built new modules and search for a professional social network in the Middle East, with PHP, Symfony and Elasticsearch in a Scrum team.

    PHPSymfonyDoctrinejQuery+4
    View details