Mubarak Elagib ME monogram
Mubarak Elagib

Mubarak Elagib

Senior Integration Engineer

Integration & Solution Architect

in production · 400+ branches · 12+ partners

The space between systems

Integration Architecture
Built for Production. Ready for AI.

I architect and build Azure-native integration platforms with .NET, connecting ERP systems, marketplaces, payments, and loyalty programs.

My work supports 400+ branches and 12+ partners. I have extended this work with a production AI agent for e-commerce operations.

View Case StudiesGet in TouchDownload Resume
Azure FunctionsService BusAzure SQL.NETC#Agentic AI

400+

Retail Branches Connected

40%

Less Manual Order Handling

60%

Less Partner Onboarding Time

12+

Partner & Platform Integrations

10+

Years of Experience

Career Journey

From developer to architect.

From teaching and freelance development in Sudan to enterprise platforms in Saudi Arabia, my work has grown across government, banking, energy, and retail.

  1. Sep 2023 — Present

    Retail & E-CommerceCurrent

    Senior Integration Engineer · Azure Integration Architecture

    Abdullah Al-Othaim Markets · Riyadh, Saudi Arabia

    Architecting the Azure-native integration platform connecting 400+ branches with 12+ marketplace, payment, and loyalty partners — now extended into production Agentic AI.

  2. Jun 2022 — Aug 2023

    Energy

    Senior Software Engineer · Backend and Architecture

    SITE · Riyadh, Saudi Arabia

    Designed and delivered the Energy Information Center Platform for the Ministry of Energy, using ASP.NET Core, Clean Architecture, and Domain-Driven Design.

  3. Feb 2020 — Mar 2022

    Banking

    Senior .NET Full-Stack Developer · Banking Systems

    Omdurman National Bank · Khartoum, Sudan

    Modernized critical banking applications from .NET Framework to .NET Core and built secure REST/SOAP integrations with external partners.

  4. Jan 2017 — Jan 2020

    Government

    Full-Stack .NET Developer · Government Systems

    National Information Center (NIC) · Khartoum, Sudan

    Developed enterprise web applications for government departments on a modular N-tier architecture, translating business requirements into deployable solutions with analysts and infrastructure teams.

  5. Apr 2015 — Dec 2016

    Freelance

    Freelance Software Developer

    Self-employed · Khartoum, Sudan · Remote

    Delivered custom web applications, database-driven systems, and internal tools for small businesses and individual clients. Managed requirements, database design, development, deployment, and ongoing support using C#, ASP.NET, Entity Framework, SQL Server, and JavaScript.

  6. Apr 2014 — Apr 2015

    Academia

    Teaching Assistant · Computer Science & Programming

    Gadarif University · Gedarif, Sudan

    Taught undergraduate courses and practical labs in C#, object-oriented programming, data structures, algorithms, and software engineering. Mentored students through coursework and academic software projects.

End-to-End Ownership

From architecture to production operations.

I take responsibility for how integrations are designed, delivered, and operated, including the data and cloud infrastructure they depend on.

Architecture

System design · contracts · integration patterns

Engineering

.NET · ASP.NET Core · Azure Functions · APIs

Data

Azure SQL · schemas · stored procedures · performance

Delivery

CI/CD · environments · infrastructure · releases

Operations

Monitoring · incident response · reliability · optimization

Case Studies

Here's what I've built.

Selected production systems, with the business problems, architecture decisions, and operational outcomes behind each one.

Unified Marketplace Integration Platform

Flagship
Event-DrivenScheduled API PollingPartner-Controlled WorkflowsCross-Cloud (AWS → Azure)Bidirectional Sync

The Problem

ERP, POS, and inventory systems needed to exchange orders, stock, pricing, and promotions with Amazon, Noon, HungerStation, Jahez, AliExpress, and Trendyol. Integrations combined events, scheduled API polling, and multi-step workflows controlled by the partner. Each model introduced different requirements for sequencing, retries, duplicate prevention, and recovery.

My role: Designed and built the integration platform, from partner workflows and .NET services to deployment and production operations.

Outcomes & Capabilities

7 marketplace channels integrated, including Amazon Marketplace, FBA, and Seller Flex
Bidirectional sync: inbound orders + outbound inventory, pricing, and promotion feeds
Resilient pipelines with retry, backoff, idempotency, and per-channel fault isolation
Automated synchronization through event-driven and scheduled workflows, according to each partner's integration model

Architecture at a glance

  1. 1

    Partner channels

    Orders, stock, prices & promotions

  2. 2

    Integration workflows

    Events, polling & orchestration

  3. 3

    .NET processing

    Validate, transform & deduplicate

  4. 4

    Business systems

    Azure SQL, ERP & POS

Conceptual inbound flow. Outbound feeds run from business systems to partner channels; explore each path below.

Key decision: Use partner-specific workflows around a shared integration backbone, with duplicate checks before internal writes.

Explore architecture

Amazon models: Marketplace · FBA · Seller Flex. Selected event-driven paths are shown below; polling and partner-controlled workflows vary by integration.

Amazon event flow
Amazon cross-cloud

Amazon SQS

Marketplace · FBA

events
AWS

AWS Lambda

Cross-cloud event bridge

cross-cloud

Service Bus

Decoupled backbone

Azure Functions

Normalize · validate

Azure SQL

Canonical data

Invoice and report pipelines use S3 separately; they are not part of the SQS event path shown here.

Azure-native order flow
Azure-native orders

Marketplace APIs

Noon · HungerStation · Jahez · AliExpress · Trendyol

webhooks / APIs

Service Bus

Per-channel isolation

Partner Functions

Transform · idempotency

Azure SQL

Orders · status · logs

ERP / POS

Internal processing

Inventory, pricing & promotion feeds
Outbound synchronization

ERP / Inventory

Stock · price · promotions

scheduled / event

Feed Functions

Chunk · throttle · retry

inventory + pricing + promotions

Marketplace Channels

Partner-specific contracts

Across these paths: correlated telemetry, retry policies, and application-level checks for duplicate processing and data consistency.

Engineering decisions

  • Amazon operates through three distinct integration models: Marketplace, FBA, and Seller Flex. Event-based AWS flows use Lambda to forward SQS messages to Azure Service Bus; invoice and report pipelines use S3 separately. Each workflow keeps its own processing and recovery requirements.
  • Service Bus as the integration backbone across all channels — decoupling external producers from internal consumers, enabling per-channel throughput control, message replay on failure, and protection against upstream rate limit spikes.
  • Transformation and normalization layer before any internal write — each marketplace payload maps to a canonical internal schema with idempotency checks, preventing duplicate processing under retries, redelivery, or throttle-driven backoff.
  • Inventory, pricing, and promotion feeds need particular care with data consistency. A failed order may affect one customer; an incorrect price can affect every unit sold until the issue is detected.

Implementation details

Amazon KSA supports Marketplace, FBA, and Seller Flex alongside separate invoice and report flows. Across the platform, ingestion follows each partner's contract: events, scheduled API polling, or multi-step orchestration. Event-based AWS flows bridge into Azure through Lambda and Service Bus; Azure Functions (.NET 8) process data and persist it to Azure SQL. Noon, HungerStation, Jahez, AliExpress, and Trendyol use dedicated Azure-native pipelines for orders and outbound synchronization. Automated feeds synchronize inventory, pricing, and promotions, with rate limit handling, retry backoff, and correlation IDs across the platform.

.NET 8Azure FunctionsService BusAPI ManagementAzure SQLApp InsightsAWS LambdaSQSS3

Payment & Loyalty Integration Layer

Gateway PatternMiddleware IntegrationOAuth2 Token ManagementUnified API Contract

The Problem

Payment and loyalty partners used different authentication flows, token lifecycles, and API contracts. Adding each partner directly to internal applications would multiply maintenance work and expose those applications to partner-specific changes. The platform needed a consistent interface for reliable transactions across BNPL, banking, and loyalty services.

My role: Designed and implemented the shared gateway contract and partner adapters for payment and loyalty integrations.

Outcomes & Capabilities

Partner onboarding time reduced by 60%
5 partners unified under one gateway contract
Partner adapters reduce changes to calling applications when adding integrations
Partner credentials stored in Key Vault with rotation support

Architecture at a glance

  1. 1

    Internal applications

    POS & digital channels

  2. 2

    API Management

    A shared calling contract

  3. 3

    Partner adapters

    Authentication & transformation

  4. 4

    Partner APIs

    Payments & loyalty

Requests and responses pass through the same gateway and partner adapter.

Key decision: Partner adapters keep partner-specific changes outside calling applications while the shared contract remains stable.

Explore architecture

Engineering decisions

  • APIM provides a consistent contract for internal systems. Partner-specific adapters handle API differences and version changes, reducing the changes needed in calling applications when the shared contract remains stable.
  • A dedicated Azure Function handles each partner's authentication, token lifecycle, and request/response transformation. This separation limits the impact of partner-specific failures and makes each adapter easier to maintain.
  • Key Vault stores partner credentials with rotation support. Each partner's Azure Function handles OAuth2 authentication and token refresh, keeping secrets out of application code and separating credential storage from token lifecycle logic.

Implementation details

Internal systems send requests through APIM as a unified gateway. APIM routes to the appropriate per-partner Azure Function, which handles OAuth2 authentication, token refresh, and request/response transformation before calling the external partner API. Responses are normalized and returned end-to-end. Partners integrated: STC Qitaf, Al Rajhi Bank (Mokafaa), Tamara, Tabby, and Comarch CLM.

Azure FunctionsAPI ManagementOAuth2Key VaultApp Insights.NET 8REST APIs

Observability & Reliability Architecture

Distributed TracingStructured LoggingShared Resilience PlatformOpenTelemetry

The Problem

As the integration surface grew to 15+ distributed Azure Functions and Service Bus pipelines, failures became increasingly difficult to trace. A failed transaction could span multiple hops — APIM, Functions, Service Bus, SQL, external partner — with no correlation between logs across services. Resilience behavior was also inconsistent: each service implemented retries and error handling independently, making the platform harder to reason about and extend reliably.

My role: Designed and implemented shared instrumentation, correlation, and resilience policies across the integration platform.

Outcomes & Capabilities

Full end-to-end trace coverage across 15+ services
Centralized alerts and correlated traces support incident investigation
Resilience patterns standardized across all integration pipelines
Single correlation ID traces the full request chain across all hops

Architecture at a glance

  1. 1

    Integration services

    Logs, metrics & traces

  2. 2

    OpenTelemetry

    Shared instrumentation

  3. 3

    Monitoring

    Application Insights & Azure Monitor

  4. 4

    Investigation

    Alerts & correlated traces

The focus here is tracing failures across service boundaries and supporting incident response.

Key decision: Propagate correlation IDs across services so an incident can be investigated as one transaction.

Explore architecture

Engineering decisions

  • OpenTelemetry over the Application Insights SDK directly — vendor-neutral instrumentation means the observability backend can change without re-instrumenting 15+ services.
  • A shared platform package standardizes Polly retry and circuit-breaker policies across services. Application-level idempotency checks protect writes when messages are retried or redelivered.
  • Correlation IDs propagated across every hop — one trace ID surfaces the full request chain from APIM through Functions, Service Bus, SQL, and external partner calls, without reconstructing timelines manually.

Implementation details

Azure Functions and Service Bus workflows emit structured logs and traces through OpenTelemetry into Application Insights and Azure Monitor. A shared Polly package standardizes retry and circuit-breaker policies. Azure Monitor alerts on anomalies as well as errors, helping the team investigate problems before they spread to downstream systems.

OpenTelemetryApplication InsightsAzure MonitorPollyService BusServerless

Agentic AI

In production

Marketplace Assistant

Ask questions. Understand your operations.

An AI assistant that helps the e-commerce team track orders, review sales, and investigate fulfillment issues — in Arabic or English.

I designed and built the complete system, from the bilingual chat interface to the AI agent, backend integrations, and data layer.

What the team can do

  • Orders & invoices

    Track order progress, review processing history, and retrieve POS invoices.

  • Sales & performance

    Compare sales by partner or branch, and find the best-selling products.

  • Branches

    Find branches by name and check which are active for each partner.

  • Products & fulfillment

    Look up item prices and identify unfulfilled products by branch or partner.

  • Availability & feed updates

    Check item availability and see when branch feeds were last updated.

  • Partner settings

    View partner configuration and per-item order quantity limits.

Supporting operations across 6 partners

  • Amazon
  • HungerStation
  • Jahez
  • Trendyol
  • Speedi
  • Nana

Item availability checks currently cover Amazon, HungerStation, and Speedi. Other capabilities depend on each partner’s available data.

Putting AI & LLMs to work in daily operations

The assistant connects large language models (LLMs) to business data, turning natural-language questions into operational answers. It helps the team understand performance, investigate issues, and make informed decisions through one conversational interface.

How I built it

Azure AI Foundry handles the conversation and tool selection. A custom MCP server on Azure Functions connects the agent to marketplace data in Azure SQL through dedicated stored procedures.

Architecture at a glance

  1. 1

    Ask a question

    Arabic or English

  2. 2

    Select a tool

    Azure AI Foundry agent

  3. 3

    Retrieve data

    MCP tools & stored procedures

  4. 4

    Present the result

    Data cards + separate explanation

The tools provide read-only access to operational data; the agent interprets the question and explains the results.

Key decision: Connect the language model to operational data through defined tools, with order cards rendered directly from tool results.

  • Azure AI Foundry
  • MCP Server
  • Azure Functions
  • Azure SQL
  • Read-only tools

What I Work With

My engineering toolkit.

Cloud & Engineering

C# · .NET · ASP.NET Core · Azure Functions · Logic Apps · API Management · Event Grid · Event-Driven Architecture · Domain-Driven Design

Integration

Marketplace integrations · FinTech and loyalty systems · Service Bus · REST APIs · Webhooks · Scheduled API polling · Workflow orchestration

Data

Azure SQL · SQL Server · Azure Synapse Analytics · Stored procedures · Schema design · Automated data pipelines

Reliability & AI

Observability · Distributed tracing · Retry strategies · Idempotency · Agentic AI & tool orchestration

Credentials

Boomi Certified Integration Professional

Boomi (Dell Technologies) · 2024

Certified

Testimonials

LinkedIn recommendations from people I've worked with.

All Recommendations
MA

Mohammad Al Haj

Head of E-Commerce Partnerships, Abdullah Al-Othaim Markets

“I had the pleasure of working closely with Mubarak on several marketplace integration projects at Al Othaim, including Amazon, Noon, and Hungerstation. From the start, he brought a sharp technical mind, clear communication, and a deep understanding of API structures and backend workflows. What really stood out was his ability to troubleshoot complex issues under tight deadlines and collaborate effectively across business and tech teams. We successfully launched integrations that directly impacted our e-commerce performance and operational efficiency — Mubarak is a rare mix of technical excellence and team spirit.”

Worked on the same team · July 2025

LinkedIn Profile
AO

Ahmad Osta

Applications Manager, Abdullah Al-Othaim Markets

“I am delighted to recommend Mubarak for his exceptional skills and contributions. He is a valuable asset and added value to any development team. He is always willing to share his knowledge and support team members, fostering a positive and productive work environment.”

Managed Mubarak directly · April 2024

LinkedIn Profile
MD

Mohammed Daggas

AI Experience Manager, DEEP.SA

“Mubarak is one of the best Developers that I have worked with, he gives meaning to the sentence "just think it and I'll do it". Extremely knowledgeable in what he does and always looking to improve, anyone would be lucky to have him in his team.”

Managed Mubarak directly · October 2023

LinkedIn Profile

Writing

I share what I learn.

Technical posts in Arabic on integration architecture, resilience, observability, and AI systems — drawn from my production work.

All Posts

Community

Sharing knowledge. Building communities.

I help graduates connect what they learn with the demands of software engineering work. Through the Sudanese Initiative For Open Training, mentoring, and technical workshops, I have supported practical skills and the transition into professional roles.

Community roles & volunteering

  • Sep 2017 — Sep 2019

    Co-Founder

    Sudanese Initiative For Open Training

    Co-founded a free training and mentorship initiative for Sudanese graduates, helped establish its visual identity, and delivered two community programs focused on practical skills and career readiness.

  • Apr 2019

    Mentor / Speaker

    Zafar Training Center

    Mentored graduates through the Graduate Entrepreneurship Program, sharing practical guidance on software careers, industry expectations, and the transition into professional roles.

  • Mar 2019 — May 2019

    Mentor / Speaker

    National Information Center

    Delivered technical training and mentoring for computer science students and early-career professionals, strengthening software engineering skills and career awareness.

The Programming Path — Photo 1
1 / 3
Graduates & Aspiring Developers2019

The Programming Path

A workshop covering learning paths, in-demand career tracks, frameworks & technologies, and how to get the most out of training courses.

👥 50+ graduates and aspiring developers attended

National Software Center — Entrepreneurship for Programmers Program
Telecom Tower, Khartoum, Sudan
Web Development Training — Photo 1
1 / 3
Government IT Engineers2018

Web Development Training

A specialized training course designed to build web development capacity for technical staff working in government institutions across Sudan.

👥 30+ government IT engineers attended

National Information Center — National Software Team
Khartoum, Sudan

Principles

The principles I design by.

How I approach reliability, data integrity, and operational risk when designing integrations.

01

Resilience by Design

I design for partner outages, delayed messages, and retries from the start. Circuit breakers and failure isolation limit disruption; idempotency checks protect against duplicate processing during recovery.

02

Observability First

I use distributed tracing, structured logs, and correlation IDs to follow transactions across services, locate failures, and support production incidents.

03

Data Integrity Always

The most damaging failures can run quietly and produce the wrong results. I prioritize data consistency and duplicate prevention, especially in pricing and inventory feeds where one incorrect value can affect many transactions.

04

Business Impact Drives Decisions

I evaluate architecture decisions by their operational impact: less manual order handling, faster partner onboarding, and simpler recovery. Results include a 40% reduction in manual order handling and a 60% reduction in partner onboarding time.

About

Building reliable systems in the space between platforms.

I am a Riyadh-based Senior Integration Engineer focused on integration and solution architecture. Across 10+ years in Sudan and Saudi Arabia, my work has spanned government, banking, energy, retail, and fintech. The common challenge is the space between systems, where data, contracts, and business processes meet.

At Abdullah Al-Othaim Markets, I architect and build an Azure-native platform connecting 400+ branches with 12+ marketplace, payment, and loyalty partners. I own the full lifecycle: architecture, cloud infrastructure, .NET implementation, deployment, observability, and production reliability.

Operating this platform has taught me to look beyond visible failures: a workflow can keep running while producing incorrect results. My current focus is extending enterprise integration with Agentic AI, tool orchestration, and workflows that help teams operate, diagnose, and automate these systems.

Get in Touch

Let's talk architecture.

Get in touch to discuss integration architecture, a consulting engagement, or a production challenge. Share the context and what you are trying to achieve.

MubarakElagib@gmail.com LinkedInRiyadh, Saudi Arabia