English | Simplified Chinese
If you liked this repo or if it helped you, please give a star ⭐️ for this repository. That will not only help strengthen our community but also improve the skills of developers to learn Silky framework 👍. Thank you very much.
The Silky framework is designed to help developers quickly build a microservice development framework through simple code and configuration under the .net platform.
Build general business microservice applications through the Generic Host of the .net framework, internal Communicate through the rpc implemented by dotnetty. During the message transmission process, the message is communicated within the same cluster through rpcToken, and the rpc communication supports ssl encryption.
Through the Web Host of .net build a service host that provides access to the outside world ( Gateway), when the http request or the ws session request arrives at the host, the routing entry of the service cluster is resolved through the built-in middleware, and the rpcToken is specified, and the built-in load balancing algorithm and routing addressing and The hosts inside the cluster communicate with rpc.
In the process of rpc communication, Silky uses interceptors and Undo Log logs to implement TCC distributed transactions to ensure the final consistency of data.
In the development and design process, the design and ideas of various excellent open source products have been borrowed and absorbed. Here, the author expresses his tribute and gratitude to the ancestors.
- Learn the Silky framework through Developer Documentation.
- Use silky.samples project to familiarize yourself with how to build a microservice application using the Silky framework.
- Familiarize yourself with the configuration properties of the Silky framework through the Configuration document.
-General agent host: business microservice host, the microservice cluster communicates through the RPC protocol within the microservice cluster, and cannot communicate with the outside of the cluster -Web agent host: Provide Http access port to the outside of the cluster. When the http request arrives, it communicates with the host inside the cluster through the RPC protocol, which is usually used as a gateway -WebSocket agent host: a business microservice host with the ability to provide websocket communication
- Responsible for the initialization process of the Silky host
- Service registration and analysis
- Responsible for module analysis and loading
- Module dependency settings
- Register service through the module
- Pass module pre-initialization method or release resources
- Routing analysis and maintenance of the distributed application cluster routing table through the registry
- Generate restful style through service entries
- Support for generating online webapi documents through Swagger
- Support performance monitoring of http requests through Miniprofiler
- Automatically verify parameters through filters during RPC call
- Support the verification of input parameters through features
- Support input parameter verification through Fluent
- Use dotnetty as the underlying communication component
- Use Zookeeper as the service registry
- Use Castle.Core.AsyncInterceptor to generate dynamic proxy
- Support cache interception during service call
- Support JSON, MessagePack, ProtoBuf encoding and decoding methods
- Support custom filters during Rpc call (client filter:
IClientFilter, server filter:IServerFilter)
- Support load balancing routing methods such as polling, random routing, hash consistency, etc.
- Support failure callback
- Use Polly to realize service fusing and retry
- Support service failover
- Support removing unhealthy services
- Disable external access to services through configuration support
The service governance module will continue to be updated
- Realize distributed transactions through TCC
- Ensure the final consistency of data through timed operations and Undolog
- Realize link tracking of calls between microservices through SkyApm
- Realize identity authentication based on Jwt
- Support custom interface authentication
- Use EfCore to implement data access components
- Implement a module that supports websocket communication through websocket-sharp
- Use madelson/DistributedLock to implement distributed locks
- Improve documentation
- Added service management dashboard
- Added CLI command line tool
- Use silky framework to implement a rights management system
- Support file upload and download
- One of the easiest ways to contribute is to participate in discussions and discuss issues. You can also contribute by submitting Pull Request code changes.