Technical insights, problem-solving notes, and best practices from real-world projects.
Explore the asynchronous processing architecture behind Shopify webhooks with BullMQ, including queue isolation, Worker concurrency control, exponential backoff retries, dead-letter queues, state management, and message replay to build a reliable and recoverable production-grade processing system.
Learn how to build a reliable Shopify webhook pipeline with HMAC verification, idempotency, event persistence, BullMQ queues, asynchronous workers, retry strategies, dead-letter queues, state management, and event replay for a resilient data synchronization layer.
Rather than rebuilding an entire Shopify store from scratch, we adopted a progressive migration strategy. The first phase focuses on building a reliable data synchronization layer using webhooks, asynchronous workers, scheduled snapshots, retry mechanisms, dead letter queues, and message replay. This foundation keeps Shopify running while continuously syncing products, customers, and orders into an internal database, enabling future modules to be migrated safely and incrementally.
Based on real project experience, this article explains how we built @raytonx/nest-scheduler on top of @nestjs/schedule to handle task reentry, duplicate execution in multi-instance deployments, lock renewal, and scheduler observability in a more consistent way.
A practical guide to resolving common Google Search Console issues like "Page with redirect" and "Duplicate, Google chose different canonical than user" in Next.js multilingual setups.
In Next.js + Supabase projects, even with generateStaticParams configured, pages can still be treated as SSR if @supabase/ssr is used. This article explains why SSG fails in practice and how to fix it.
Based on real project experience, this article explains why we did not just use @nestjs/config and instead built our own ConfigModule to better handle multi-environment loading, Zod-based validation, config overrides, and more predictable deployments.
A practical workflow for connecting requirements, development, and delivery with Notion and GitHub, helping remote teams keep projects structured, visible, and transparent for clients.
A practical guide to building a Next.js content system with GitHub, MDX, SSG, caching, and Webhooks, including a pattern for partial pre-rendering with authenticated full-content loading.
A practical guide to building a Redis-based cache service in NestJS, including key design, hash-based storage, field-level TTL handling, and patterns that support production-ready backend systems.
In this article, we explain how to manage configuration elegantly in a NestJS project using the @nestjs/config module. We cover how to support multiple environments such as development, testing, and production, and how to implement schema validation to ensure configuration safety before the app starts.
This article shares our real-world experience in efficiently syncing data from MongoDB to ClickHouse via RabbitMQ for real-time business analytics. It’s suitable for building lightweight, low-latency heterogeneous data analysis pipelines.
This post introduces how to build a cleanly modular, scalable, and high-performance data analytics platform using NestJS. The system integrates Kafka, ClickHouse, and RabbitMQ for efficient data ingestion and processing.
A practical guide to integrating Feishu Bitable with business systems, including webhook-based automation, message listening for non-public environments, and API-based read/write operations with the Feishu SDK.
As our business continued to grow, user scale and data volumes expanded exponentially. The original monolithic synchronous write approach began to expose significant performance bottlenecks. This post shares how we evolved from a single MongoDB architecture to a Kafka + ClickHouse analytics platform in production, and the lessons we learned.
A guide to implementing efficient multilingual support in a Next.js App Router project using next-intl, including directory structure, routing, language switching, and best practices.
While next-intl encourages using JSON files for translation, we found object-based structures loaded via getI18n to be more flexible and maintainable—especially for dynamic content like FAQs and service lists.