Moleculer transporter selection for low-traffic cost optimization

Reducing operational costs for low-traffic workloads in Moleculer often involves minimizing external dependencies and network overhead. The framework provides several transporter options, including local, Redis, and NATS, each with different resource implications.

While the local transporter eliminates external infrastructure costs and network latency, it restricts the architecture to a single node. Transitioning to a distributed model using Redis or NATS introduces infrastructure overhead but allows for horizontal scaling.

There is uncertainty regarding the optimal transition point between these transporters when the primary goal is minimizing memory and CPU idling costs without sacrificing the ability to scale during occasional traffic spikes.

• Which transporter configuration offers the lowest baseline resource footprint while maintaining a path to horizontal scaling?
• How does the memory overhead of the Redis transporter compare to the local transporter in a minimal service deployment?