Backend engineer · Belgrade, Serbia

Building software. Exploring everything else.

I’m Bane, a backend software engineer working primarily with Python. I design and build systems for complex workflow execution, real-time processing, and reliable operation in production.

Explore my work

5+ years of engineering experience.

Backend work, in practice.

Trickest

Backend Developer

–Present

At Trickest, a cybersecurity platform, I've spent the past five years designing and building backend systems, and staying involved as they evolved in production. Some of the most interesting challenges came later, when growing complexity and real-world traffic called for a different approach.

  1. Architecture

    Making complex workflows reusable

    As our workflows grew more complex, maintaining them and reusing logic across them became increasingly difficult. I designed and built reusable workflow modules — each one a workflow that can be used as a building block inside another, with support for multiple levels of nesting.

    To execute these nested workflows, I implemented recursive graph expansion, reconnecting inputs, outputs, and dependencies into a single execution graph without changing the original workflow definitions.

    I also preserved the connection between individual jobs, their original modules, and the exact versions used in each run. This lets users inspect what happened inside each module, even after it has changed.

  2. SYSTEM RELIABILITY

    Building and scaling an audit logging system

    A client needed a reliable record of activity across our platform. I designed and built an audit logging service from scratch using FastAPI and ClickHouse. As traffic grew, the service began running out of memory, restarting, and losing audit events.

    I redesigned the ingestion pipeline around RabbitMQ and batched writes to ClickHouse, separating incoming events from database processing.

    The redesign stabilized memory usage at around 40% in production, ending the repeated restarts and associated event loss we had been seeing.

  3. REAL-TIME SYSTEMS

    From polling to event-driven updates

    Our API servers kept hitting 100% CPU. The culprit was constant frontend polling for execution updates, which triggered expensive database queries. As the number of jobs grew, optimizing those queries alone wasn't enough.

    I designed and implemented an event-driven update system using Redis Pub/Sub and Server-Sent Events. Instead of repeatedly fetching large lists of jobs, clients could receive lightweight updates as their states changed.

    This eliminated the recurring CPU saturation caused by polling, reduced database load, and made execution updates more responsive.

  4. DISTRIBUTED SYSTEMS

    Keeping job state reliable at scale

    Our execution engine ran the jobs, but the backend had to keep an accurate record of what happened to each one. I built the RabbitMQ and Celery consumers that processed engine events into job records, status changes, and results.

    As executions grew larger, workers began running out of memory, and job updates were getting lost. I traced a major source of the problem to a Django ORM lazy load that repeatedly pulled entire workflow definitions into memory.

    I changed the consumers to reuse workflow data across an execution instead of repeatedly loading it for each job. To avoid unnecessary database work, I batched job updates rather than writing them one by one. Together, these changes brought memory usage under control and stopped the worker failures and missing updates we had been seeing.

A little beyond the code.

Travel, food, history & live events

I have a habit of planning trips around oddly specific things, and food is often one of them. Khinkali near Ananouri Fortress in Georgia, bánh mì on little plastic stools along the sidewalks of Vietnam, or pizza a portafoglio in Naples. I love cooking too, so some of those discoveries eventually make their way into my own kitchen — with varying degrees of success.

Sometimes, something I've read is reason enough to make a trip. Gdańsk, Guernica, and Sarajevo drew me in because of their place in modern history. I wanted to see those places for myself, not just read about what happened there. But my curiosity goes further back, too — from the ruins of Pompeii to Mount Circeo, traditionally associated with Circe from Homer's Odyssey.

A race, a match, or a concert can be just as good a reason to travel. I've watched Formula 1 at Imola, surrounded by Ferrari's tifosi, and the Euro 2024 final among the crowds at Madrid's Plaza de Cibeles. At BBK Live in Bilbao, I finally heard Air and Massive Attack, two acts I'd wanted to see for years. Hearing Metallica launch into "Enter Sandman" at Madrid's Metropolitano Stadium was another moment I'd looked forward to. And closer to home, there's EXIT — nights of live music within the walls of Petrovaradin Fortress in Novi Sad.

Let’s talk.

About backend engineering, an idea, or just to say hello.