java分布式dubbo_Dubbo 是一个分布式的、高性能的RPC框架

最新推荐文章于 2024-04-17 01:15:12 发布

nlp小白菜

最新推荐文章于 2024-04-17 01:15:12 发布

阅读量119

点赞数

文章标签： java分布式dubbo

本文链接：https://blog.csdn.net/weixin_33205735/article/details/114444633

版权

2.7.0

Requirements: Java 8+ required

Please check here for notes and possible compatibility issues for upgrading from 2.6.x or lower to 2.7.0.

New Features

Enhancement of service governance rules.

Enriched Routing Rules.

Conditional Routing. Supports both application-level and service-level conditions.

Tag Routing. Newly introduced to better support traffic isolation, such as grey deployment.

Decoupling governance rules with the registry, making it easier to extend. Apollo and Zookeeper are available in this version. Nacos support is on the way...

Application-level Dynamic Configuration support.

Use YAML as the configuration language, which is more friendly to read and use.

Externalized Configuration. Supports reading dubbo.properties hosted in remote centralized configuration center - centralized configuration.

Simplified registry URL. With lower Registry memory use and less notification pressure from Service Directory, separates Configuration notification from Service Discovery.

Metadata Center. A totally new concept since 2.7.0, used to store service metadata including static configuration, service definition, method signature, etc.. By default, Zookeeper and Redis are supported as the backend storage. Will work as the basis of service testing, mock and other service governance features going to be supported in OPS.

Asynchronous Programming Model (only works for Dubbo protocol now)

Server-side asynchronous support, with an AsyncContext API works like Servlet 3.0.

Asynchronous filter chain callback.

Serialization Extension: Protobuf.

Caching Policy Extension: Expiring Cache.

Enhancements / Bugfixes

Load Balancing strategy enhancement: ConsitentHash #2190, LeastActive #2171, Random #2597, RoundRobin #2650.

Third-party dependency upgrading.

Switch default remoting to Netty 4.

Switch default Zookeeper client to Curator.

Upgrade Jetty to 9.x.

IPV6 support #2079.

Performance tuning, check hanging requests on a closed channel, make them return directly #2185.

Fixed the serialization problem of JDK primitive types in Kryo #2178.

Fixed the problem of failing to notify Consumer as early as possible after the Provider side deserialization failed #1903.

Upgrading and Compatibility Notifications

We have always keep compatibility in mind during the whole process of 2.7.0. We even want old users to upgrade with only on pom version upgrade, but it's hard to achieve that, especially when considering that we have the package renamed in this version, so we had some tradeoffs. If you only used the Dubbo's most basic features, you may have little problems of upgrading, but if you have used some advanced features or have some SPI extensions inside, you'd better read the upgrade notifications carefully. The compatibility issues can be classified into the following 5 categories, for each part, you can find the detailed dos and don'ts in this documentation.

Interoperability between 2.7.0 and lower versions

Package renaming

com.alibaba.dubbo -> org.apache.dubbo

Simplification of registered URLs

Service Governance Rules

Configuration

环境要求：需要Java 8及以上版本支持

请在这里了解关于升级2.7.x版本的注意事项和兼容性问题

New Features

服务治理规则增强。

更丰富的服务治理规则，新增应用级别条件路由、Tag路由等

治理规则与注册中心解耦，增加对Apollo等第三方专业配置中心的支持，更易于扩展