microsurging/surging

Health v2 · maintenance only

Adoption not part of the score

3263 stars · 921 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Surging is a distributed microservice engine for .NET Core providing a lightweight, high-performance, modular RPC pipeline with service registration and discovery via ZooKeeper or Consul. It integrates load balancing, fault tolerance, an event bus, distributed caching, and supports transports like DotNetty, RabbitMQ, and gRPC with MessagePack or protobuf serialization.

Use cases

• build microservices in .NET Core with RPC between services
• service registration and discovery with Consul or ZooKeeper
• add an API gateway in front of microservices
• publish/subscribe messaging via an event bus with RabbitMQ or Kafka
• load balancing and fault tolerance for internal service calls
• distributed caching with consistent hashing
• containerized CI/CD deployment of services on Docker and Kubernetes

When to choose

• you are building a .NET Core microservice system needing high-performance RPC
• you want built-in service discovery, load balancing, and an event bus in one engine
• you prefer modular middleware (cache, eventbus, storage) with domain-driven service modules

When to avoid

• your stack is not .NET/.NET Core
• you need a mainstream framework with a very large community and ecosystem (e.g., Service Mesh or ASP.NET Core + gRPC)
• you only need simple REST APIs without service mesh features

Facets

framework · maturity active

rpc microservices api-gateway message-queue serialization caching service-discovery middleware tracing microservices backend apis dotnet cross-platform dotnet-core service-engine event-bus load-balancing consul zookeeper netty rabbitmq grpc skywalking messaging docker kubernetes

Member repositories

For agents

markdown · JSON · MCP: product_card(name="microsurging/surging")