Skip to content
View mostafa6266's full-sized avatar

Block or report mostafa6266

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
mostafa6266/README.md

Mostafa Mohamed

Architecture is the craft. Performance is the obsession.

Software Architecture · Distributed Systems · Blockchain & DeFi

Cairo, Egypt · LinkedIn · Email


Beyond the happy path

Five years working across backend platforms, identity verification, financial infrastructure, and blockchain systems.

The interesting challenges rarely sit inside a single function. They appear between services, across database boundaries, under concurrent load, or when an external dependency stops behaving as expected.

Architecture

Service boundaries, data ownership, authentication, authorization, and communication between services.

The difficult part isn't choosing between microservices and a modular monolith. It's deciding which responsibilities belong together, which need isolation, and how the system maintains consistency without unnecessary coupling.

Architecture should make the system easier to understand, change, and operate, not simply introduce more components.

Performance

Query plans, indexing, caching, asynchronous processing, concurrency, and profiling.

Most performance improvements start by understanding where time and resources are actually spent. Sometimes that means removing database round trips or reducing unnecessary work. Other times, it means changing an execution path.

Python for backend services and data pipelines. Rust for processing paths where profiling justifies the added complexity.

Reliability

Distributed systems fail in ways that aren't always obvious.

A request can time out after succeeding. A message can be delivered twice. A worker can restart halfway through a job. An external provider can become unavailable while everything else remains healthy.

Retries, idempotency, timeouts, backpressure, recovery, and observability are part of the design, not additions after deployment.

Blockchain & DeFi

Solana-based infrastructure for market data, on-chain transaction analysis, and automated trading.

Work includes DEX integrations, liquidity and price aggregation, grid trading, arbitrage engines, and transaction analysis.

The engineering challenges revolve around event freshness, execution latency, transaction construction, large-scale data processing, and the reliability of systems operating against constantly changing market conditions.

Selected technologies

Python · Rust · TypeScript · Go

Django · FastAPI · PostgreSQL · Redis · ClickHouse

RabbitMQ · Kafka · Docker · AWS · Linux


Make it work. Understand why it works. Know how it fails.

Pinned Loading

  1. httpcore httpcore Public

    Forked from encode/httpcore

    A minimal HTTP client. ⚙️

    Python

  2. httpx httpx Public

    Forked from encode/httpx

    A next generation HTTP client for Python. 🦋

    Python

  3. celery/celery celery/celery Public

    Distributed Task Queue (development branch)

    Python 29.1k 5.3k

  4. vitalik/django-ninja vitalik/django-ninja Public

    💨 Fast, Async-ready, Openapi, type hints based framework for building APIs

    Python 9.2k 624

  5. celery/kombu celery/kombu Public

    Messaging library for Python.

    Python 3.2k 1.1k

  6. celery/py-amqp celery/py-amqp Public

    amqplib fork

    Python 315 206