lmammino/distributed-jwt-cracker

Ability to restore the server with its internal state after a failure or a manual shutdown

Open

#2 opened on Oct 1, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (7 forks)github user discovery
enhancementhacktoberfesthelp wanted

Repository metrics

Stars
 (60 stars)
PR merge metrics
 (PR metrics pending)

Description

This requires the usage of some form of data persistency. A JSON file should be more than ok given that the state can be represented by the nextBatch and the list of batches currently under processing.

Contributor guide

Research direction
Understand the current internal state (nextBatch and batches under processing) and implement a JSON file persistence mechanism. On server startup, read the file to restore state; on shutdown or failure, write the state to the file. Ensure file operations are safe from corruption (e.g., atomic writes).
Tech stack
javascriptnodejs
Domain
backenddistributed systems
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75