Hosted logging vs self-hosted ELK for small Node.js SaaS teams
The article advises that a small Node.js marketplace should generally use a hosted logging service rather than run its own ELK stack. Self-hosting only makes sense when control over storage, networking, or query behavior is a documented requirement worth the added operational burden. The author argues the key measure for a pricing-rule rollout is how fast someone can tell a faulty rule apart from an unhealthy service, not how much data is stored. The recommended approach is to emit structured, pseudonymous decision events through a replaceable transport, keeping the event format vendor-neutral. Such events should record the flag, variant, rule version, and totals while excluding personal data and entire request bodies.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in