/**

Node.js is the backend runtime I know inside and out — I've built production APIs with Hono, NestJS, and Express, plus background job systems with BullMQ.

Hono on Bun was a revelation for Hurivuri — lightweight, fast, and the middleware pattern feels cleaner than Express. I built the full e-commerce REST API with it: SSLCommerz payment processing, multi-courier integrations (Pathao, RedX, Steadfast), an affiliate commission engine, and role-based access control.

BullMQ is the unsung hero of my backend work — I use it for email delivery, Meilisearch index synchronization, payment webhook handling, and scheduled maintenance tasks. Reliable job processing backed by Redis with configurable retry and exponential backoff.

For Solang Playground I went with NestJS — the structure, dependency injection, and decorators make sense when the backend needs more organization. Prisma handles the PostgreSQL layer for compilation tracking and analytics. Moonly's backend runs GraphQL resolvers with BullMQ raffle scheduling and Redis-cached NFT metadata.

Whether it's a lightweight Hono API or a full NestJS application, Node.js gives me the flexibility to match the backend architecture to the problem. I've used both Node.js and Bun runtimes in production and each has its strengths.

*/