change test configuration to test interface type registry (#411)

* change test configuration to test interface type registry

* update java samples
8 files changed
tree: f78616c04a733c5d0da6c1fb2932cb1d240a9d83
  1. .github/
  2. .images/
  3. .run/
  4. api/
  5. apisix/
  6. build/
  7. config-api/
  8. configcenter/
  9. context/
  10. direct/
  11. error/
  12. filter/
  13. game/
  14. generic/
  15. helloworld/
  16. integrate_test/
  17. logger/
  18. metrics/
  19. otel/
  20. registry/
  21. rpc/
  22. skywalking/
  23. tracing/
  24. .asf.yaml
  25. .gitignore
  26. ci.sh
  27. go.mod
  28. go.sum
  29. HOWTO.md
  30. HOWTO_zh.md
  31. integrate_test.sh
  32. LICENSE
  33. README.md
  34. README_zh.md
  35. start_integrate_test.sh
  36. waiting_launch.sh
README.md

Dubbo Golang Examples

CI

What It Contains

  • apisix: apache/apisix and Dubbo-go example
  • config-api: show how to use dubbogo by APIs without configuration
  • configcenter: uses of different config centers, including zookeeper and nacos at present.
  • context: how to transfer request context between multiple producers/consumers
  • direct: A direct invocation example.
  • error/triple: triple sample with hessian2/protobuf
  • filter: Some examples of different filter, including custom_filter and tpslimit
  • game: game service example
  • generic: A generic invocation example
  • helloworld: A 101 example
  • integrate_test: dubbogo github action integrate test use cases
  • logger: dubbogo logging
  • metrics: show how to collect dubbogo prometheus metrics
  • otel/trace: show how to use opentelemetry as dubbogo tracing tool
  • registry: show how to use etcd/nacos/polaris/zookeeper as dubbogo registry
  • rpc: dubbo directory display dubbo protocol communication
  • seata: A seata example
  • skywalking: show how to integrate skywalking into dubbogo
  • tracing: tracing example

How To Run

Pls refer How To Run for the instructions.

How to contribute

If you want to add more samples, pls. read on:

  1. Create new sub directory and give it an appropriate name for your new sample. Pls follow the layout of the existing sample if you are not sure how to organize your code.
  2. Make sure your sample work as expected before submit PR, and make sure GitHub CI passes after PR is submitted. Pls refer to the existing sample on how to test the sample.
  3. Pls provide README.md to explain your samples.