refactor/dubbo-security grpc dependency replace (#14004)

* refactor(): Replace grpc by triple

* refactor(): delete useless code

* refactor(): fix code style & fix bug

* fix(): pom & code style

* fix(): inappropriate change

* fix(): error use volatile
5 files changed
tree: b2ed1405e24d4cdbce48445b08a8544eac6df510
  1. .github/
  2. .mvn/
  3. codestyle/
  4. dubbo-cluster/
  5. dubbo-common/
  6. dubbo-compatible/
  7. dubbo-config/
  8. dubbo-configcenter/
  9. dubbo-demo/
  10. dubbo-dependencies/
  11. dubbo-dependencies-bom/
  12. dubbo-distribution/
  13. dubbo-maven-plugin/
  14. dubbo-metadata/
  15. dubbo-metrics/
  16. dubbo-plugin/
  17. dubbo-registry/
  18. dubbo-remoting/
  19. dubbo-rpc/
  20. dubbo-serialization/
  21. dubbo-spring-boot/
  22. dubbo-test/
  23. dubbo-xds/
  24. .artifacts
  25. .asf.yaml
  26. .editorconfig
  27. .gitattributes
  28. .gitignore
  29. .licenserc.yaml
  30. CHANGES.md
  31. CODE_OF_CONDUCT.md
  32. codecov.yml
  33. CONTRIBUTING.md
  34. Jenkinsfile
  35. Jenkinsfile.sonar
  36. LICENSE
  37. licenseCheck.sh
  38. mvnw
  39. mvnw.cmd
  40. NOTICE
  41. pom.xml
  42. README.md
  43. SECURITY.md
README.md

Apache Dubbo Project

Build and Test For PR Codecov Maven License Average time to resolve an issue Percentage of issues still open

Apache Dubbo is an easy-to-use Web and RPC framework that provides multiple language implementations(Java, Go, Rust, Node.js, Web) for communication, service discovery, traffic management, observability, security, tools, and best practices for building enterprise-ready microservices.

We are now collecting Dubbo user info to help us to improve Dubbo further. Kindly support us by providing your usage information on Wanted: who's using dubbo, thanks :)

Architecture

Architecture

  • Consumer and provider communicate with each other using RPC protocol like triple, tcp, rest, etc.
  • Consumers automatically trace provider instances registered in registries(Zookeeper, Nacos) and distribute traffic among them by following traffic strategies.
  • Rich features for monitoring and managing the cluster with dynamic configuration, metrics, tracing, security, and visualized console.

Getting started

Follow the instructions below to learn how to:

Programming with lightweight RPC API

5 minutes step-by-step guide

Dubbo supports building RPC services with only a few lines of code while depending only on a lightweight SDK (<10MB). The protocol on the wire can be Triple(fully gRPC compatible and HTTP-friendly), Dubbo2(TCP), REST, or any protocol of your choice.

Building a microservice application with Spring Boot

5 minutes step-by-step guide

It's highly recommended to start your microservice application with the Spring Boot Starter dubbo-spring-boot-starter provided by Dubbo. With only a single dependency and yaml file, and optionally a bunch of other useful spring boot starters, you can enable all of the Dubo features like service discovery, observability, tracing, etc.

Next, learn how to deploy, monitor, and manage the traffic of your Dubbo application and cluster.

More Features

Get more details by visiting the links below to get your hands dirty with some well-designed tasks on our website.

Which Dubbo version should I use?

Dubbo3JDKDependenciesDescription
3.3.0-beta1.8 ~ 17dependency list- Unstable version
- Features
   - Triple - gRPC and cURL compatible.
   - Rest-style programming support.
   - Spring Boot Starters.
3.2.51.8 ~ 17dependency list- Stable version (active)
- Features
  - Out-of-box metrics and tracing support.
  - Threadpool Isolation
  - 30% performance
  - Native Image
3.1.111.8 ~ 11dependency listStable version (not active)
Dubbo2JDKDependenciesDescription
2.7.231.8dependency listEOL
2.6.x, 2.5.x1.6 ~ 1.7EOL

Contributing

See CONTRIBUTING for details on submitting patches and the contribution workflow.

How does the Dubbo Community collaborate?

The Dubbo Community primarily communicates on GitHub through issues, discussions, and pull requests.

  • Issues: We use issues to track bugs and tasks. Any work-related item is associated with an issue.
  • Discussions: We use discussions for questions, early proposals, and announcements. Any idea-related item is associated with a discussion.
  • Pull Requests: We use pull requests to merge a set of changes from contributors into Dubbo.

We have also implemented a project board to monitor all the items.

Any essential changes should be discussed on the mailing list before they happen.

Seeking for help

If you have questions such as:

  • What is Dubbo?
  • How do I use Dubbo?
  • Why did an unexpected result occur?

Please start a discussion at https://github.com/apache/dubbo/discussions.

However, if you encounter the following situations:

  • You‘re certain there’s a bug that Dubbo needs to fix,
  • You believe a feature could be enhanced,
  • You have a detailed proposal for improving Dubbo,

Please open an issue at https://github.com/apache/dubbo/issues.

To ask effective questions, we recommend reading How To Ask Questions The Smart Way first.

Contribution

  • Browse the “help wanted” tasks in the Dubbo project board.
  • Participate in discussions on the mailing list. See the subscription guide.
  • Respond to queries in the discussions.
  • Resolve bugs reported in issues and send us a pull request.
  • Review existing pull requests.
  • Enhance the website. We typically need:
    • Blog posts
    • Translations for documentation
    • Use cases showcasing Dubbo integration in enterprise systems.
  • Improve the dubbo-admin.
  • Contribute to the projects listed in the ecosystem.
  • Any other forms of contribution not listed above are also welcome.
  • If you're interested in contributing, please send an email to dev@dubbo.apache.org to let us know!

For further details, please refer our guide about how to contribute Dubbo.

Reporting bugs

Please follow the template for reporting any issues.

Reporting a security vulnerability

Please report security vulnerabilities to us privately.

Contact

  • WeChat: apachedubbo
  • DingTalk group: 37290003945
  • Mailing list: guide
  • Twitter: @ApacheDubbo
  • Security issues: please mail to us privately.

Contributing

See CONTRIBUTING for details on submitting patches and the contribution workflow.

How can I contribute?

  • Take a look at issues with tags marked Good first issue or Help wanted.
  • Join the discussion on the mailing list, subscription guide.
  • Answer questions on issues.
  • Fix bugs reported on issues, and send us a pull request.
  • Review the existing pull request.
  • Improve the website, typically we need
    • blog post
    • translation on documentation
    • use cases around the integration of Dubbo in enterprise systems.
  • Improve the dubbo-admin/dubbo-monitor.
  • Contribute to the projects listed in ecosystem.
  • Other forms of contribution not explicitly enumerated above.
  • If you would like to contribute, please send an email to dev@dubbo.apache.org to let us know!

Reporting bugs

Please follow the template for reporting any issues.

Reporting a security vulnerability

Please report security vulnerabilities to us privately.

Dubbo ecosystem

Language

License

Apache Dubbo is licensed under the Apache License Version 2.0. See the LICENSE file for details.