Reference
Library Comparison
How RoExpress stacks up against the other major Roblox networking libraries. Every library has a different philosophy | use this to pick the right tool.
Honest comparison. Each library is good at what it does. The right choice depends on your game's architecture, not which has more features.
Feature matrix
| Feature | RoExpress | BridgeNet2 | ByteNet | Zap |
|---|---|---|---|---|
| HTTP-style routing | ✓ GET/POST/PUT/DELETE | ✗ | ✗ | ✗ |
| Route params | ✓ :id=number | ✗ | ✗ | ✗ |
| Wildcard routes | ✓ feed/* | ✗ | ✗ | ✗ |
| Middleware | ✓ app:Use() | ✗ | ✗ | ✗ |
| Rate limiting | ✓ Token bucket | ✗ | ✗ | ✗ |
| Compression | ✓ LZ77 → Deflate | ✗ | ✗ | ✗ |
| Server push | ✓ Reliable | ✓ | ✗ | ✗ |
| Unreliable broadcast | ✓ Broadcast module | ✓ | ✓ | ✓ |
| Binary serialization | ✓ Codec + Stream | ✗ | ✓ | ✓ |
| Tick-rate channel sync | ✓ Stream | ✗ | ✓ | ✓ |
| Lag compensation | ✓ Stream.Rewind | ✗ | ✗ | ✗ |
| Exploit detection | ✓ Tamper | ✗ | ✗ | ✗ |
| Internal event bus | ✓ Bridge | ✗ | ✗ | ✗ |
| Port isolation | ✓ Ports | ✗ | ✗ | ✗ |
| Benchmark module | ✓ | ✗ | ✗ | ✗ |
| TypeCoercer | ✓ | ✗ | ✗ | ✗ |
| Code generation | ✗ | ✗ | ✗ | ✓ |
| Schema-defined types | Partial (Stream) | ✗ | ✓ | ✓ |
| Single RemoteEvent | ✓ (default) | ✓ | ✗ | ✗ |
When to use RoExpress
- You want the structured request/response model of an HTTP API | routes, params, middleware, status codes
- You need multiple features from one package: request handling + push + rate limiting + tamper + stream
- Your team is already familiar with Express.js or similar | the mental model transfers directly
- You want lag compensation without building it from scratch
When to use others
- ByteNet / Zap | if you need maximum throughput via generated, statically-typed binary protocol. Both use code generation for zero-overhead packing.
- BridgeNet2 | if you only need a thin reliable remote wrapper with minimal overhead.
- Roll your own | if your game has a single tight loop and the structure RoExpress adds would be overhead with no benefit.
See also
The Story | why RoExpress was built · Design Decisions | the reasoning behind specific choices · Research Papers | academic foundations