docs: tell a source-backed performance story - #28
Open
cmilesio wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add a full-width Performance page that tells GoForj's local-first driver story through an animated benchmark hero, exact local-path measurements, configuration-to-infrastructure boundary comparisons, interactive logarithmic driver charts for Cache, Queue, Events, and Storage, and a shared net/http comparison.
Add a generated performance dataset that consumes committed library benchmark JSON, records source revisions and SHA-256 hashes, and fails the docs build when checked-in data drifts. Link the page from primary navigation, Operations, and homepage proof.
Why
GoForj's performance advantage is architectural: Apps can use real cache, queue, event, and storage contracts in process or on local storage, then move only the boundary that needs coordination, persistence, or distribution. Business services do not need to be rewritten just because the driver changes.
The page keeps this credible by naming every measurement boundary, showing what external infrastructure buys, distinguishing producer-side queue dispatch from job completion, and treating container/emulator results as controlled comparisons rather than production forecasts.