humanmade / humanmade/local-pinpoint

Queue Elasticsearch writes

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
JavaScript
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

To better reflect the real service and also improve performance and reduce resource usage it'd be good to find a way to queue the writes to Elasticsearch up.

Can explore using a child/worker thread if it's possible to re-bind from a fresh function call.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the Elasticsearch write entry points and reviewing how the local testing server currently performs those writes. Investigate whether a child or worker thread can safely handle queued writes and define completion as writes being queued while preserving service behavior and reducing resource usage.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, javascript
Domain
backend, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.