Google Git
Sign in
apache / dubbo-go-samples / refs/tags/v1.5.6-rc2
commitac38818cd13ec2536fe59e51523a4fde3aee37da[log] [tgz]
authorAlexStocks <alexstocks@foxmail.com>Tue Mar 16 15:19:40 2021 +0800
committerAlexStocks <alexstocks@foxmail.com>Tue Mar 16 15:19:40 2021 +0800
tree20d6bba76ff5e9b700926ebb9d15ebf0cfaf8f9b
parent101f7e9abd2a995c977d0965d0b17166281cf547 [diff]
adjust import sequence in nacos
1 file changed
tree: 20d6bba76ff5e9b700926ebb9d15ebf0cfaf8f9b
  1. .github/
  2. .images/
  3. .run/
  4. async/
  5. attachment/
  6. build/
  7. chain/
  8. config-api/
  9. configcenter/
  10. context/
  11. direct/
  12. docker/
  13. filter/
  14. general/
  15. generic/
  16. group/
  17. helloworld/
  18. metric/
  19. multi-registry/
  20. multi-zone/
  21. registry/
  22. router/
  23. seata/
  24. shop/
  25. tracing/
  26. .asf.yaml
  27. .gitignore
  28. ci.sh
  29. go.mod
  30. go.sum
  31. HOWTO.md
  32. HOWTO_zh.md
  33. integrate_test.sh
  34. LICENSE
  35. README.md
  36. README_zh.md
  37. start_integrate_test.sh
README.md

Dubbo Golang Examples

CI

What It Contains

  • async: An async example.
  • attachment: An attachment example, to show how to use attachment to pass user data from the client to the server.
  • configcenter: uses of different config centers, including zookeeper, apollo and nacos at present.
  • direct: A direct invocation example.
  • filter: Some examples of different filter, including custom_filter and tpslimit
  • general: A general example
  • generic: A generic invocation example
  • helloworld: A 101 example
  • multi_registry: A multi-registry example
  • registry: uses of different registres, including kubernetes, nacos, etcd and service-discovery
  • router: router examples, including condition and tag
  • seata: A seata example
  • shop: Shop sample
  • 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.