ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #moleculer
When developing a Moleculer service locally, setting validator: false (or omitting the flag) lets the broker skip AJV schema validation for action parameters, so invalid requests are accepted without error. The same configuration deployed to production allows unvalidated payloads to reach service actions, which can cause unexpected behavior, security risks,
Pagination Strategy Selection The goal is to implement efficient result set retrieval using Moleculer's underlying ORM capabilities for paginated queries. Constraint Uncertainty The constraint is determining the most robust pagination method when dataset size is unknown but high-volume deep paging is a possibility. Offset-based pagination relies on `setMaxRe
Cache strategy decision for Moleculer services Goal: select a caching mechanism that meets the latency budget of a production API while ensuring cached data survives process restarts and is consistent across multiple instances. Constraints: the native in‑memory cache delivers sub‑millisecond read times but is lost on restart and does not share state between
I'm designing a Moleculer service where several actions are wrapped with the built-in cacher, and I'm trying to pin down exactly when a cached action response stops being served. Assume a recent Moleculer 0.14.x release with the default in-memory cacher. My understanding is that the cacher keys entries from the action name plus params, and that a TTL control
Goal Reduce operational cost for a low‑traffic Moleculer microservice by using the Local Transporter to avoid external broker fees while leveraging the built‑in cache mixin to cut downstream calls. Constraint / Uncertainty Increasing cache TTL improves hit rate and saves compute, but raises memory consumption; with the Local Transporter all services run in‑p
The goal is to clarify how Moleculer’s Redis transporter behaves when an action throws an error and no custom retries is defined. The framework’s documentation states that the default retry policy is indefinite, which may lead to continuous re‑delivery attempts and uncertain back‑pressure semantics under sustained failure conditions. Constraints include the
When using the moleculer-db package, the standard find action supports limit and offset parameters to paginate results. While the parameter validator can enforce a maximum page size to prevent oversized requests, the underlying database execution behavior varies significantly based on the offset value.In many adapters, such as SQL-based or MongoDB, a high of
Goal: Choose a pagination strategy for a Moleculer service that must return large result sets efficiently while providing stable pages when data is inserted or deleted between requests. Limit/offset pagination is available out‑of‑the‑box through the moleculer‑db mixin’s find action, but it can skip or duplicate rows when the underlying collection changes and
Goal Ensure that a failed service upgrade can be rolled back without losing messages or leaving in‑flight requests unresolved, while respecting Moleculer’s lack of automatic draining and the transporter’s delivery guarantees. When the new version is stopped via broker.stopService , ongoing calls are aborted unless custom logic waits for them to finish, and t
redis
nodejs