{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_bundle","feature":"bundle","name":"LLM article bundle","what":"Paste-ready package: body + claims + sources + voxels + provenance + manifest + constitution.","contains":"body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest","slug":"oip-what-is-a-load-balancer","urls":{"read":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/bundle?format=markdown"},"how_to_use":"Paste into any LLM. Read §SELF first. Write back via ingest or claim endpoints in llm_manifest.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","urls":{"read":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/topology"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"ingest","name":"Ingest protocol","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","urls":{"write":"https://miscsubjects.com/api/protocol/ingest"}},{"id":"claim_post","name":"Claim post protocol","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by.","urls":{"read":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"id":"llm_manifest","name":"LLM manifest","what":"Machine-readable read/write contract for external LLMs.","urls":{"read":"https://miscsubjects.com/api/articles/llm-manifest"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"bundle","name":"LLM article bundle","what":"Paste-ready package: body + claims + sources + voxels + provenance + manifest + constitution.","why":"Every feature is auditable collective intelligence","how":"Paste into any LLM. Read §SELF first. Write back via ingest or claim endpoints in llm_manifest.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/bundle?format=markdown"},"imessage":null,"router":null,"related":[{"id":"topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."},{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"ingest","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node."},{"id":"claim_post","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by."},{"id":"llm_manifest","what":"Machine-readable read/write contract for external LLMs."}],"not_medical_advice":true},"bundle_version":1,"generated_at":"2026-07-04T22:37:19.083Z","slug":"oip-what-is-a-load-balancer","title":"What Is a Load Balancer?","url":"https://miscsubjects.com/a/oip-what-is-a-load-balancer","register":"oip_protocol","tags":["oip","protocol"],"posted_at":"2026-07-04T18:30:24.592Z","updated_at":"2026-07-04T19:01:15.824Z","body":"## What It Is\n\nA **load balancer** is a traffic director that routes incoming requests across multiple backend servers. It keeps any single server from drowning under demand.\n\nIt is a **stateless gateway** that sits at the edge of a fleet, making a single decision for every request: *which machine handles this?*\n\n## Why It Matters\n\nSystems break at the edges. Not in the code. In the traffic.\n\nA load balancer prevents one server from becoming a bottleneck and a single point of failure. It replaces the fragility of a lone server with the resilience of a distributed group.\n\nThe deeper point: **who decides where traffic goes is a question of power.** In a closed system, the decision is hidden in vendor magic. In an open system, the decision is transparent, deterministic, and auditable.\n\nLoad balancing is one of the foundational primitives of distributed systems. Without it, horizontal scaling is a fiction.\n\n## How It Works\n\n**Step 1. A request arrives.**\n\nA user hits an IP or a DNS name. That request lands on the load balancer first.\n\n**Step 2. The balancer picks a backend.**\n\nUsing a rule, it selects one server from a pool. The rules are simple and explicit:\n\n- **Round-robin:** Take turns. Server A, then B, then C, then A again.\n- **Least connections:** Route to the server with the fewest active requests.\n- **Weighted round-robin:** Server A gets 70% of traffic, Server B gets 30%.\n- **IP hash:** The same client IP always hits the same server. Useful for session affinity.\n- **Health-based:** Do not send traffic to a server that is down or unhealthy.\n\n**Step 3. The request forwards.**\n\nThe balancer opens a connection to the chosen backend and pipes the request through.\n\n**Step 4. The response returns.**\n\nThe backend replies. The balancer passes the response back to the client. The client does not know the backend exists.\n\n**Step 5. Health checks run continuously.**\n\nEvery backend is probed on a cadence. If a server fails its health check, it is removed from the pool. If it recovers, it is reinstated. This is automatic. This is the mechanism that makes the system self-healing.\n\n## The Contract\n\nThe interface of a load balancer is formal and unambiguous.\n\n**Input:** A request from a client.\n\n**Output:** That request routed to a healthy backend, and the backend response returned to the client.\n\n**Invariants:**\n\n- No request is dropped unless every backend is down.\n- A backend is removed from the pool if it fails its health check.\n- A backend is restored to the pool if it passes its health check.\n- The routing rule is deterministic and reproducible for the same inputs.\n- The client is never aware of the backend.\n\n**Failure modes:**\n\n- If all backends are down, the balancer returns a 503.\n- If a backend fails mid-request, the balancer retries on a different backend (if configured).\n- If the balancer itself is a single point of failure, the architecture is broken.\n\n## Real Examples\n\n**NGINX reverse proxy with upstream.**\n\nYou define an `upstream` block with three backends. NGINX routes each request in round-robin. The configuration is a flat file. The behavior is auditable.\n\n**Cloudflare Load Balancer.**\n\nGlobal traffic routing across data centers. The balancer makes a geographic decision: a user in London hits a server in London, not a server in Los Angeles. The health check is a synthetic HTTP probe every 15 seconds.\n\n**AWS Elastic Load Balancer (ALB).**\n\nLayer 7 routing. The balancer inspects the HTTP path: `/api/*` goes to the API fleet. `/static/*` goes to the static fleet. Different rules, different backends, one entry point.\n\n**Kubernetes Service.**\n\nA Kubernetes `Service` with `type: LoadBalancer` provisions an external IP and routes traffic to matching pods. If a pod dies, the Service stops sending it traffic. The health check is the liveness probe.\n\n**haproxy on bare metal.**\n\nIn high-frequency trading or telecommunications, haproxy runs on a pair of physical machines with a floating virtual IP. Keepalived shifts the IP between two balancer machines if one fails. Zero downtime. Zero ambiguity.\n\n## Common Mistakes\n\n**Treating the load balancer as invisible.**\n\nIt is a machine. It has a config. It can be misconfigured. A bad rule routes all traffic to one server. A missing health check lets a dead server keep eating requests. Audit the balancer.\n\n**Ignoring the balancer as a single point of failure.**\n\nIf you have one load balancer, you have one load balancer. If it dies, everything dies. Run two. Use a floating IP. Use DNS failover. Redundancy at the edge matters.\n\n**Session affinity without a session store.**\n\nIf a server handles a login and a sticky IP route sends the next request to a different server, the user is logged out. Session affinity is a hack. Use a shared session store or a stateless token.\n\n**Health checks that are too optimistic.**\n\nIf the health check pings `/health` and the server returns 200 but is actually on fire, the balancer thinks the server is fine. Health checks must test the actual capacity to serve, not just the capacity to return 200.\n\n**Connection draining during deploys.**\n\nIf you deploy a new backend and kill the old one instantly, active requests are dropped. Connection draining waits for in-flight requests to finish before removing a server from the pool. This is not optional.\n\n## Connection to OIP\n\nThe Open Internet Protocol is built on three principles: **open, deterministic, auditable.**\n\nA load balancer is the embodiment of all three.\n\n**Open:** The routing rule is not a secret. It is in a config file. Any operator can read it, modify it, and understand why traffic flows the way it does.\n\n**Deterministic:** The same request, under the same conditions, routes to the same backend. The rule is not probabilistic. It is not magic. It is code.\n\n**Auditable:** Every routing decision is a log line. Every health check is a timestamp. Every backend failure and recovery is recorded. You can trace the behavior of the system over time without asking a vendor.\n\nIn an OIP system, the load balancer is not a vendor appliance. It is a contract, a set of rules, and a transparent decision engine that anyone can inspect, verify, and replace.\n\n\n## Connection to the Grain Philosophy\n\nThis protocol is part of the [Open Inventory Protocol](/a/philosophy) — a living system of self-describing voxels that serves the Grain philosophy. The OIP is the interface. The philosophy is the core.\n","claims":[],"sources":[],"voxels":{"slug":"oip-what-is-a-load-balancer","counts":{"voxels":0,"sources":0,"edges":0},"note":"slim bundle — full voxels at /api/articles/oip-what-is-a-load-balancer/voxels"},"constitution":{"url":"https://miscsubjects.com/api/articles/constitution"},"provenance":[],"contributions":[],"topology":null,"slim":true,"ledger_totals":{"claims":0,"sources":0,"exported_claims":0,"exported_sources":0},"question_graph":{"slug":"oip-what-is-a-load-balancer","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"verification":{"provenance":{"valid":true,"entries":0,"head":"genesis"},"sources":{"valid":true,"entries":0,"head":"genesis"}},"counts":{"claims":0,"sources":0,"provenance":0,"contributions":0,"questions":0,"evidence_ingests":0,"voxel_edges":0},"llm_manifest":{"version":"1","site":"https://miscsubjects.com","purpose":"Peptide evidence articles with hash-chained source ledgers, tiered claims, and a question graph. LLMs should READ bundles/URLs and WRITE back via ingest — never invent doses.","read":{"human_page":"https://miscsubjects.com/a/oip-what-is-a-load-balancer","bundle_json":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/topology","question_graph":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/question-graph","sources":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/sources","provenance":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/provenance","contributions":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/contributions","graph_topology":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/graph-topology?question={question}","voxels":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","health":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/health","repair":"POST https://miscsubjects.com/api/protocol/repair","list_articles":"https://miscsubjects.com/api/articles","graph_canvas":"https://miscsubjects.com/graph.html?slugs=oip-what-is-a-load-balancer","graph_yield":"https://miscsubjects.com/api/graph?slugs=oip-what-is-a-load-balancer&layer=yield","obsidian_vault":"https://miscsubjects.com/api/articles/obsidian-vault?slugs=oip-what-is-a-load-balancer","graph_query":"https://miscsubjects.com/api/v1/query?from=oip-what-is-a-load-balancer&kind=claim&where=tier=human"},"ask":{"description":"Answer only from topology; creates a question_node with gaps.","api":"POST https://miscsubjects.com/api/protocol/ask","body":{"slug":"{slug}","question":"string"},"imessage":"oip-what-is-a-load-balancer|your question","router_tag":"[ARTICLE_ASK]oip-what-is-a-load-balancer|question[/ARTICLE_ASK]","auth":"x-terminal-key header for API; iMessage/WhatsApp via miscsubjects build"},"ingest":{"description":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","api":"POST https://miscsubjects.com/api/protocol/ingest","body":{"slug":"{slug}","evidence":"paste text","question_node_id":"optional qn_..."},"imessage":"ingest oip-what-is-a-load-balancer|q:{node_id}|paste evidence","router_tag":"[ARTICLE_INGEST]oip-what-is-a-load-balancer|evidence[/ARTICLE_INGEST]","tiers":["human","preclinical","anecdotal","mechanistic","speculative"]},"claim":{"description":"Prompt-injection style POST — one claim voxel with who_claims + posted_by provenance.","api":"POST https://miscsubjects.com/api/protocol/claim","body":{"slug":"{slug}","text":"one assertion","tier":"human|preclinical|anecdotal|mechanistic|speculative","who_claims":"study author, platform, or model id","source_ids":"optional [s1]"},"imessage":"claim oip-what-is-a-load-balancer|tier|assertion — who claims it?","router_tag":"[ARTICLE_CLAIM]oip-what-is-a-load-balancer|tier|assertion[/ARTICLE_CLAIM]","slots":["what_it_is","who_claims_what","what_is_known","what_is_unknown","mechanism","limitations","disclaimer"]},"tiers":{"human":0.8,"preclinical":0.5,"anecdotal":0.3,"mechanistic":0.3,"speculative":0.1},"invariants":["Self-explaining — every API JSON has _self; every paste widget has §SELF; root index at /api/articles/system-map","Append-only — revisions preserved at ?rev=n","Source chain verifies integrity, not truth","Answers must cite claim ids and source ids from topology","Not medical advice"],"constitution":{"version":1,"principle":"Articles are voxel graphs of claims — not prose blobs. Every assertion is a claim atom with tier, weight, source_ids, and posted_by provenance.","slots":[{"id":"what_it_is","required":true,"answers":"What is this peptide/stack/condition?"},{"id":"who_claims_what","required":true,"answers":"Who claims what — study authors, platforms, n=?"},{"id":"what_is_known","required":true,"answers":"What is known with tier labels (human/preclinical/anecdotal)"},{"id":"what_is_unknown","required":true,"answers":"What is NOT known — explicit gaps"},{"id":"mechanism","required":false,"answers":"Proposed mechanism (mechanistic tier only)"},{"id":"limitations","required":true,"answers":"Limits of evidence — no dose advice"},{"id":"disclaimer","required":true,"answers":"Not medical advice"}],"claim_rules":["One claim = one falsifiable assertion. No compound claims.","Every claim must declare tier: human|preclinical|anecdotal|mechanistic|speculative|system.","system tier = architecture/design axioms (not biological mechanism). Use for protocol self-definition.","Sourced claims must cite source_ids from the hash-chained ledger.","Unsourced claims must set source_status: unsourced and why_material.","posted_by is mandatory on every new claim (model id, human, or channel).","No medical advice, no doses, no 'you should take'.","Bad information is retracted (status:retracted), never deleted — retraction event stays on ledger.","Adversary challenges link via challenges[] / challenged_by[] — target may be downweighted.","Leaked secrets are scrubbed to [REDACTED:secret-leak] with scrub_events tombstone — honest audit trail."],"source_rules":["Every source is a voxel edge: type, url, exact quote, summary, found_by, accessed_at.","Sources hash-chain — prev/hash on append.","Anecdotal sources must name platform (reddit|x|youtube|imessage|user_entry)."],"ontology_rules":["Peptide articles (bpc-157, tb-500) are tree roots.","Condition articles (bpc-157-glp1-gut-damage) branch from peptides.","Stack articles (wolverine-stack-glp1) compose peptides — never duplicate peptide mechanism prose.","If an article has no parent embeds and is not a root peptide → sprawl candidate.","Misstep = duplicate scope with another slug; merge or reparent via embeds."],"post_protocol":{"claim":"POST /api/protocol/claim","source":"POST /api/protocol/sources","ingest":"POST /api/protocol/ingest","webhook":"POST /api/articles/<slug>/webhook {kind:claim|source}","imessage_claim":"claim {slug}|{tier}|your assertion — who claims it, source?","imessage_ingest":"ingest {slug}|evidence paste"}},"this_article":{"slug":"oip-what-is-a-load-balancer","url":"https://miscsubjects.com/a/oip-what-is-a-load-balancer","bundle_url":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/bundle?format=markdown"}},"api_urls":{"bundle":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/topology","voxels":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","question_graph":"https://miscsubjects.com/api/articles/oip-what-is-a-load-balancer/question-graph","ask":"https://miscsubjects.com/api/protocol/ask","ingest":"https://miscsubjects.com/api/protocol/ingest","claim":"https://miscsubjects.com/api/protocol/claim","system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown"}}