Expand description
§Refractium
A high-performance, lightweight L4 protocol multiplexer.
refractium allows you to route incoming TCP and UDP traffic to different backends
based on the protocol identification (magic bytes, SNI, etc.). It supports
dynamic protocol registration, load balancing, and health monitoring.
§Core Features
- TCP & UDP Support: Multiplex both stream and packet-based traffic.
- Protocol Identification: Built-in support for HTTP, HTTPS (with SNI), SSH, DNS, and FTP.
- Dynamic Routing: Add custom protocols using simple patterns or complex logic.
- Load Balancing: Distribute traffic across multiple backends with health checks.
- Graceful Shutdown: Built-in support for cancellation tokens.
§Quick Start
use refractium::core::Refractium;
use refractium::protocols::ProtocolRegistry;
use refractium::protocols::http::Http;
use std::collections::HashMap;
use std::sync::Arc;
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let mut registry = ProtocolRegistry::new();
registry.register(Box::new(Http));
let mut routes = HashMap::new();
routes.insert("Http".to_string(), vec!["127.0.0.1:8080".to_string()]);
let refractium = Refractium::builder()
.registries(Arc::new(registry), Arc::new(ProtocolRegistry::new()))
.routes(routes, HashMap::new())
.build();
refractium.run_tcp("0.0.0.0:80".parse()?).await?;
Ok(())
}Re-exports§
pub use crate::core::types;pub use crate::core::Refractium;pub use crate::core::RefractiumBuilder;pub use crate::errors::RefractiumError;pub use crate::errors::Result;
Modules§
- core
- Core logic for proxying and routing.
- errors
- Error types and result aliases.
- macros
- Internal macros for protocol definition.
- protocols
- Protocol implementations and identification logic. Protocol identification and registry logic.
Macros§
- define_
protocol - Macro to define a new protocol by implementing the
RefractiumProtocoltrait. - refractium_
debug - Internal debug logging macro.
- refractium_
error - Internal error logging macro.