Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This pull request renames and restructures the NodeCore documentation page. The file pages/nodecore.mdx is replaced with pages/nodecore-open-source-rpc-stack.mdx, with the navigation metadata updated accordingly in _meta.json.
Changes:
- Renamed documentation file from
nodecore.mdxtonodecore-open-source-rpc-stack.mdx - Expanded content from 81 to 127 lines with improved organization and additional context
- Enhanced Meta tags with specific SEO title and description
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| pages/nodecore.mdx | Removed old NodeCore documentation file |
| pages/nodecore-open-source-rpc-stack.mdx | Added new, restructured NodeCore documentation with expanded content, clearer use case descriptions, and improved SEO metadata |
| pages/_meta.json | Updated file reference from "nodecore" to "nodecore-open-source-rpc-stack" |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+16
to
+127
| ## **Why teams deploy NodeCore** | ||
|
|
||
| Organizations adopt NodeCore to: | ||
|
|
||
| - Eliminate dependency on single RPC providers | ||
| - Control routing logic and performance policies internally | ||
| - Reduce infrastructure costs at scale | ||
| - Run hybrid setups combining self-hosted and third-party nodes | ||
| - Maintain uptime during upstream outages | ||
|
|
||
| ## **Design Goals** | ||
|
|
||
| NodeCore is built around four core infrastructure principles: | ||
|
|
||
| ### **1. Cost Efficiency** | ||
|
|
||
| Smart caching combined with price-aware routing minimizes redundant upstream calls and optimizes provider spend without compromising performance. | ||
|
|
||
| ### **2. Performance-Aware Routing** | ||
|
|
||
| NodeCore continuously evaluates provider latency, error rates, and throughput to select the most suitable upstream for every request. Underperforming providers are automatically deprioritized. | ||
|
|
||
| ### **3. Resilient Error Handling** | ||
|
|
||
| Automated retries, hedged parallel requests, and circuit-breaker logic protect applications from upstream instability and long-tail latency spikes. | ||
|
|
||
| ### **4. Operational Simplicity** | ||
|
|
||
| NodeCore centralizes routing, usage analytics, and provider monitoring into a unified control layer. It simplifies multi-provider infrastructure management. | ||
|
|
||
| ## **Who is NodeCore for?** | ||
|
|
||
| ### **Best fit for:** | ||
|
|
||
| - Web3 infrastructure and DevOps teams running their own nodes | ||
| - dApps with backend-originated traffic from one or few regions | ||
| - Enterprises requiring on-prem or VPC-contained RPC traffic | ||
| - Teams combining multiple RPC vendors for redundancy and cost control | ||
|
|
||
| ### **Less ideal for:** | ||
|
|
||
| - Applications with globally distributed, browser-originated traffic | ||
| - Frontend-heavy dApps requiring edge routing worldwide | ||
| - Teams seeking fully managed, no-ops RPC infrastructure | ||
|
|
||
| In these cases, a managed global routing solution such as NodeCloud may be more appropriate. | ||
|
|
||
| ## **Key Features** | ||
|
|
||
| ### **1. Intelligent Cost-Aware Routing** | ||
|
|
||
| Routes requests using real-time latency, error-rate, and pricing metrics to balance performance and cost. | ||
|
|
||
| ### **2. Multi-Chain / Multi-Protocol Support** | ||
|
|
||
| Compatible with Ethereum-like chains, Solana, Cosmos, Bitcoin, TON, Polkadot, Near, Starknet, and more across JSON-RPC, WebSocket, gRPC, and REST. | ||
|
|
||
| ### **3. Aggressive, Correctness-Aware Caching** | ||
|
|
||
| Supports memory, Redis, and Postgres caching layers to reduce redundant traffic and upstream load. | ||
|
|
||
| ### **4. Real-Time Metrics & Observability** | ||
|
|
||
| Exports Prometheus metrics and OpenTelemetry traces out-of-the-box for deep performance monitoring. | ||
|
|
||
| ### **5. Streaming-First Response Handling** | ||
|
|
||
| Streams large payloads by default to minimize memory footprint and improve throughput. | ||
|
|
||
| ### **6. Resilient Error Handling** | ||
|
|
||
| Retries, hedging, and circuit-breaker protections ensure consistent uptime. | ||
|
|
||
| ### **7. NodeCloud Bridge (Optional)** | ||
|
|
||
| Sync API keys, usage budgets, and analytics with NodeCloud for hybrid deployments. | ||
|
|
||
| ## **System Architecture** | ||
|
|
||
| NodeCore sits between client applications and upstream RPC providers: | ||
|
|
||
| **Client → NodeCore Load Balancer → Cache Layer → Providers → Metrics & Tracing** | ||
|
|
||
| | **Component** | **Purpose** | | ||
| | --- | --- | | ||
| | Load Balancer | Accepts client RPC traffic and routes upstream | | ||
| | Routing Engine | Applies latency, cost, and reliability policies | | ||
| | Provider Adapters | Connects to JSON-RPC, WS, gRPC, REST endpoints | | ||
| | Cache Layer | Stores frequent read queries | | ||
| | Metrics & Tracing | Prometheus + OTEL observability | | ||
| | NodeCloud Bridge | Hybrid key and billing sync | | ||
|
|
||
| ## **Reliability Design Principles** | ||
|
|
||
| NodeCore is built around production resilience: | ||
|
|
||
| - No single-provider dependency (N+1 routing) | ||
| - Hedged reads to reduce long-tail latency | ||
| - Circuit breakers eject failing nodes | ||
| - Checksum-verified read caching | ||
| - Automatic rate-limit discovery | ||
|
|
||
| ## **Deployment Scenarios** | ||
|
|
||
| Common production setups include: | ||
|
|
||
| - Routing across Infura + Alchemy + self-hosted nodes | ||
| - Backend traffic balancing from a single region | ||
| - Hybrid NodeCore + NodeCloud failover | ||
| - Private RPC infrastructure for enterprise workloads | ||
|
|
||
| --- No newline at end of file |
There was a problem hiding this comment.
The heading formatting is inconsistent with the rest of the documentation. Standard markdown headings should be used without bold markers (e.g., ## Design Goals instead of ## **Design Goals**).
liringlas
approved these changes
Feb 24, 2026
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
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.
No description provided.