Optimize Kafka & NestJS Code (Quick Bug Fix)
Budget: $100 – $300 USD
Our micro-service stack runs on Node.js with NestJS and a heavy dose of Kafka messaging. While the feature set is stable, performance hiccups and a few stubborn bugs are slowing releases. I’m looking for a JavaScript specialist who can dive straight into the existing repository, profile the hot spots, and leave the codebase lean and crash-free.
Scope
• Optimise message flow inside the Kafka integration: tighten producers/consumers, improve back-pressure handling, and verify acknowledgements.
• Refactor NodeJS utility modules where memory or CPU spikes appear.
• Fix logic and lifecycle issues inside several NestJS components, making sure they cooperate cleanly with the Kafka layer.
Resources available
You’ll have full access to the repo, a Docker-based local setup, and detailed architecture docs that outline event schemas, module boundaries, and current deployment workflows. Unit tests already exist for most modules, so you can reproduce bugs quickly.
Deliverables (acceptance criteria)
– Performance report showing baseline vs. post-optimisation metrics.
– Clean, well-commented commits that resolve the identified bugs.
– Updated tests proving green builds across Kafka, NodeJS, and NestJS layers.
I value concise, self-contained PRs and clear commit messages. If you enjoy squeezing extra throughput out of JavaScript and taming flaky Kafka workflows, you’ll have fun with this one.
Scope
• Optimise message flow inside the Kafka integration: tighten producers/consumers, improve back-pressure handling, and verify acknowledgements.
• Refactor NodeJS utility modules where memory or CPU spikes appear.
• Fix logic and lifecycle issues inside several NestJS components, making sure they cooperate cleanly with the Kafka layer.
Resources available
You’ll have full access to the repo, a Docker-based local setup, and detailed architecture docs that outline event schemas, module boundaries, and current deployment workflows. Unit tests already exist for most modules, so you can reproduce bugs quickly.
Deliverables (acceptance criteria)
– Performance report showing baseline vs. post-optimisation metrics.
– Clean, well-commented commits that resolve the identified bugs.
– Updated tests proving green builds across Kafka, NodeJS, and NestJS layers.
I value concise, self-contained PRs and clear commit messages. If you enjoy squeezing extra throughput out of JavaScript and taming flaky Kafka workflows, you’ll have fun with this one.