| tag | 27bc939c4226eee4b0801300c983b3d6787bd6bd | |
|---|---|---|
| tagger | xiaoyu <549477611@qq.com> | Fri Apr 02 17:48:12 2021 +0800 |
| object | e86d41e84ee52cca1d71fb7e5252fd27b9d1edbd |
2.3.0
| commit | e86d41e84ee52cca1d71fb7e5252fd27b9d1edbd | [log] [tgz] |
|---|---|---|
| author | xiaoyu <549477611@qq.com> | Fri Apr 02 17:46:16 2021 +0800 |
| committer | xiaoyu <549477611@qq.com> | Fri Apr 02 17:46:16 2021 +0800 |
| tree | 6226116e23887a5d8c98f14e67f2ec57bf5d4e7c | |
| parent | 740c732224a5746becb05db724107af3ddba3c29 [diff] |
2.3.0-RELEASE
soul-admin : plugins and other information configuration management background
soul-bootstrap : with the startup project, users can refer to
soul-client : user fast access with Spring MVC, Dubbo, Spring Cloud.
soul-common : framework common class
soul-disruptor : based on disruptor Enclosure
soul-register-center : rpc type register for soul-client
soul-dist : build project
soul-metrics : metrics impl by prometheus.
soul-plugin : Soul provider plugin collection.
soul-spi : Soul spi define.
soul-spring-boot-starter : support for the spring boot starter
soul-sync-data-center : provider ZooKeeper, HTTP, WebSocket, Nacos to sync data
soul-examples : the RPC examples project
soul-web : core processing packages including plugins, request routing and forwarding, and so on
Soul provides plugins such as current limiting, fusing, forwarding, routing monitoring and so on.
Support HTTP, RESTFul, WebSocket, Dubbo, GRPC, Tars and Spring Cloud Proxy.
Plug-in hot plug, users can customize the development.
Selectors and rules are dynamically configured for flexible matching.
Support for cluster deployment.
Support A/B test and grayscale publishing.
Whenever a request comes in, Soul executes all open plugins through the chain of responsibility.
As the heart of Soul, plugins are extensible and hot-pluggable.
Different plugins do different things.
Of course, users can also customize plugins to meet their own needs.
If you want to customize, see custom-plugin
According to your HTTP request headers, selectors and rules are used to route your requests.
Selector is your first route, It is coarser grained, for example, at the module level.
Rule is your second route and what do you think your request should do,For example a method level in a module.
The selector and the rule match only once, and the match is returned. So the coarsest granularity should be sorted last.
All data have been cached using ConcurrentHashMap in the JVM, so it's very fast.
When the user is managing changes in the background, Soul dynamically updates the cache by listening to the ZooKeeper node, WebSocket push, HTTP longPull.
Soul has been used in our production environment,its performance and flexibility allow us to use up very cool.
In double 11, we deployed 6 clusters, which supported a large volume of our business.
In order of registration, More access companies are welcome to register at https://github.com/Dromara/soul/issues/68 (For open source users only)