Migrating Graph Operations to Apache AGE: From Writes to Reads Introduction When you move a graph workload from Neo4j to Apache AGE, the challenges don’t stop at choosing a database. The real work …

Trendyol Tech Blog offers a glimpse into the technology and engineering practices powering one of Turkey's leading e-commerce platforms. With a focus on scalability, performance, and innovation, Trendyol Tech shares insights into microservices architecture, data engineering, and machine learning. Developers can learn about building high-traffic e-commerce systems, optimizing delivery pipelines, and leveraging  technologies to drive business growth.

Trendyol Tech

A production engineering team at Trendyol shares their migration from Neo4j Enterprise to Apache AGE, a graph extension for PostgreSQL. Key decisions include consolidating multiple relationship types into a single discriminated HAS edge for simpler writes, using native SQL instead of Cypher for high-throughput writes, and replacing variable-length path queries (which bypass indexes in AGE and caused 3–5 second response times) with iterative fixed-depth traversals. Go goroutines parallelize multi-hop queries across intermediate nodes, and pointer-based map sets handle memory-efficient deduplication of overlapping results. The migration traded Neo4j's raw graph performance for PostgreSQL's operational advantages: unified infrastructure, CDC via logical replication, and predictable licensing costs.

Migrating Graph Operations to Apache AGE: From Writes to Reads

Why We Migrated from Neo4j Enterprise to Apache AGE