How does ARPC compare to gRPC in terms of performance?

ARPC is benchmarked for high performance in Go, with links to third-party benchmarks in the Performance section, but it lacks gRPC's built-in code generation and multi-language support. For pure Go projects requiring bidirectional RPC, ARPC can be faster due to its minimal overhead, but always test with your specific workload.

How to implement authentication in an ARPC server?

Authentication isn't built-in; you need to use router middleware or custom handlers. The pub/sub extension shows password-based auth, but for general use, implement a middleware that validates tokens or credentials before processing requests, as hinted in the Router Middleware examples.

Does ARPC support WebSockets or only TCP?

ARPC primarily uses TCP with custom net protocols, but WebSockets can be integrated by providing a custom dialer and connection handler. The Custom Net Protocol section allows wrapping any net.Conn, so you can adapt it for WebSockets with additional code.

What's the error handling strategy for async calls in ARPC?

For async calls, errors must be handled in callbacks; the framework doesn't provide automatic retry or circuit breaking. In CallAsync, check the context for errors in the callback, and use middleware like recovery to catch panics, as shown in the Router Middleware examples.

Can ARPC be used with Kubernetes for microservices?

Yes, but ARPC doesn't include Kubernetes-specific features; you'll need to manage service discovery, scaling, and health checks externally. Its stateless design works with container orchestration, but expect to implement these aspects yourself or with additional tools.

How to add compression or encryption middleware in ARPC?

Use coder middleware for data transformation; the README provides an example with gzip compression in the Coder Middleware section. For encryption, implement a custom coder that encrypts/decrypts payloads, leveraging the extensible middleware system.

Is ARPC suitable for real-time chat applications?

Yes, ARPC is well-suited for real-time chat due to its broadcast, two-way notify, and pub/sub features. The Web Chat Examples demonstrate this use case, showing how to handle multiple clients and push notifications efficiently.

arpc — High-Performance Go RPC Framework

What is arpc?

ARPC is a Go framework for building high-performance network applications with rich communication patterns like two-way calling, notifications, and broadcast. It solves the need for flexible, efficient remote procedure calls in distributed systems and real-time services.

Target Audience

Go developers building distributed systems, microservices, real-time applications (like chat or gaming servers), or any network service requiring bidirectional RPC.

Value Proposition

Developers choose ARPC for its combination of high performance, bidirectional communication support, and extensibility through middleware and customizations, without the overhead of larger frameworks.

More effective network communication, two-way calling, notify and broadcast supported.

Use Cases

Best For

Building real-time chat or notification servers
Implementing microservices with bidirectional RPC
Creating pub/sub systems for event-driven architectures
Developing high-performance game servers
Building custom network protocols with middleware support
Replacing or extending standard Go net/rpc with more features

Not Ideal For

Projects requiring built-in service discovery and orchestration tools
Teams that prioritize large ecosystems with extensive third-party integrations
Applications where standard HTTP/REST or gRPC with automatic code generation suffices
Rapid prototyping with minimal configuration and batteries-included features

Pros & Cons

Pros

Bidirectional Communication Patterns

Supports two-way calling and notifications, allowing both clients and servers to initiate requests and fire-and-forget messages, as detailed in the Features table for interactive directions.

High Performance Foundation

Emphasizes performance with benchmarks and optimizations like batch writes, making it suitable for real-time applications, though the README advises running tests yourself for accurate results.

Extensive Middleware Support

Offers router and coder middleware for logging, recovery, compression, and encryption, enabling easy customization without modifying core logic, as shown in the Router Middleware and Coder Middleware sections.

Built-in Pub/Sub Extension

Includes publish-subscribe patterns out of the box for event-driven architectures, with examples provided in the Pub/Sub Examples section, reducing the need for external libraries.

Flexible Customization Options

Allows custom protocols, codecs, loggers, and queue management, providing a foundation for tailored network applications, as demonstrated in sections like Custom Net Protocol and Custom Codec.

Cons

Limited High-Level Abstractions

Lacks built-in support for common distributed systems features like automatic load balancing or service discovery, requiring manual implementation for production-grade microservices.

Documentation Fragmentation

Examples and extensions are split into a separate repository (arpcex), which can make it harder to find integrated documentation and increase setup complexity for newcomers.

Smaller Ecosystem and Community

Compared to established frameworks like gRPC or rpcx, ARPC has fewer third-party tools, plugins, and community contributions, which may limit support and integration options.

Configuration Overhead

The emphasis on customization and minimal core means more boilerplate code is needed for basic setups, such as implementing authentication or error handling from scratch.

Frequently Asked Questions

What is arpc?

Target Audience

Go developers building distributed systems, microservices, real-time applications (like chat or gaming servers), or any network service requiring bidirectional RPC.

Value Proposition

Use Cases

Best For

Building real-time chat or notification servers
Implementing microservices with bidirectional RPC
Creating pub/sub systems for event-driven architectures
Developing high-performance game servers
Building custom network protocols with middleware support
Replacing or extending standard Go net/rpc with more features

Not Ideal For

Projects requiring built-in service discovery and orchestration tools
Teams that prioritize large ecosystems with extensive third-party integrations
Applications where standard HTTP/REST or gRPC with automatic code generation suffices
Rapid prototyping with minimal configuration and batteries-included features

Pros & Cons

Pros

Bidirectional Communication Patterns

Supports two-way calling and notifications, allowing both clients and servers to initiate requests and fire-and-forget messages, as detailed in the Features table for interactive directions.

High Performance Foundation

Emphasizes performance with benchmarks and optimizations like batch writes, making it suitable for real-time applications, though the README advises running tests yourself for accurate results.

Extensive Middleware Support

Built-in Pub/Sub Extension

Includes publish-subscribe patterns out of the box for event-driven architectures, with examples provided in the Pub/Sub Examples section, reducing the need for external libraries.

Flexible Customization Options

Allows custom protocols, codecs, loggers, and queue management, providing a foundation for tailored network applications, as demonstrated in sections like Custom Net Protocol and Custom Codec.

Cons

Limited High-Level Abstractions

Lacks built-in support for common distributed systems features like automatic load balancing or service discovery, requiring manual implementation for production-grade microservices.

Documentation Fragmentation

Examples and extensions are split into a separate repository (arpcex), which can make it harder to find integrated documentation and increase setup complexity for newcomers.

Smaller Ecosystem and Community

Compared to established frameworks like gRPC or rpcx, ARPC has fewer third-party tools, plugins, and community contributions, which may limit support and integration options.

Configuration Overhead

The emphasis on customization and minimal core means more boilerplate code is needed for basic setups, such as implementing authentication or error handling from scratch.

Frequently Asked Questions

arpc

What is arpc?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

arpc

What is arpc?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?