A .NET microservices framework for building distributed applications with RPC communication and service governance.
Silky is a .NET-based microservices framework that helps developers build distributed applications quickly through simple code and configuration. It provides high-performance RPC communication and a suite of service governance features like discovery, load balancing, and fault tolerance, abstracting away the complexities of remote calls.
.NET developers and teams building scalable, distributed microservices architectures who need built-in service governance and RPC capabilities.
Developers choose Silky for its seamless integration with .NET, out-of-the-box service governance, and extensible design that balances ease of use with enterprise-ready features like distributed transactions and observability.
The Silky framework is designed to help developers quickly build a microservice development framework through simple code and configuration under the .net platform.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Leverages Polly for built-in resilience patterns like retries, circuit breaking, and load balancing, reducing custom fault-tolerance code. The README highlights support for multiple strategies out-of-the-box.
Uses DotNetty for TCP-based communication with dynamic interface proxying, enabling efficient, transparent remote calls. The framework emphasizes low latency and high throughput for distributed calls.
Features plugin-based module and service loading with clear dependency management, allowing developers to customize or extend core functionality easily, as described in the modular design section.
Includes RPC token authentication, SSL encryption, and tracing for HTTP/RPC calls, providing enterprise-grade security and monitoring without additional setup, per the security and observability sections.
Requires external services like Zookeeper for service discovery and Redis for distributed transactions, adding operational complexity and deployment overhead, as shown in the quick start guide.
Primarily Chinese-language documentation and a smaller community compared to mainstream frameworks may limit accessibility and third-party integrations for global teams.
Demands detailed YAML or JSON configurations for governance features (e.g., RPC tokens, registry settings), which can be error-prone and time-consuming to manage.