supported methods:

• Detailed logics of all methods in service for users/shops/audits, http apis and remote process calls are provided
• select reviews from elasticsearch by storeID.
• select reviews from elasticsearch with not null comments.

supported methods:

• create review
• update review
• delete review
• see review details
• see all reviews created by someone

supported methods:(remote calls in review-service)

• create for reply
• update for reply
• appeal for reply

supported methods:(remote calls in review-service)

• audit for reviews
• audit for appeals

go install google.golang.org/protobuf/cmd/protoc-gen-go@latest

go install github.com/go-kratos/kratos/cmd/kratos/v2@latest

Suggest to setup data tables in your MySQL first (review_info,review_reply_info and review_appeal_info), see .sql file for details. Denote the database named review.

(unimplemented) Add cache to redis when querying for reviews.

Find a suitable version in docker official website, you need to create a account first.

git clone https://github.com/hashicorp/learn-consul-docker.git
cd datacenter-deploy-service-discovery
docker-compose up -d

Or view link for details

  docker pull canal/canal-server:latest
  docker run -d --name canal-server -p 11111:11111 canal/canal-server

  go get github.com/segmentio/kafka-go

See tutorial in link to setup kafka,zookeeper and kafka-ui in Docker

  go get github.com/elastic/go-elasticsearch/v8@latest

See tutorial in link to setup elasticsearch and Kibana in Docker

To test if http apis and grpcs works well. Find a suitable version in https://www.postman.com/, you may need to create an account for convinent use (like storing a certain http/grpc request route for multiplexing).

CREATE USER 'canal'@'localhost' IDENTIFIED BY 'canal';
GRANT ALL PRIVILEGES ON my_database.* TO 'canal'@'localhost';
FLUSH PRIVILEGES;

Enter Canal Container, execute:

vi canal-server/conf/example/instance.properties

modify the following settings and save, then canal is able to catch changes in database "review":

canal.instance.master.address=host.docker.internal:3306 (when MySQL is deployed locally, if it is in Docker, use 127.0.0.1 or localhost instead.)
canal.instance.tsdb.dbUsername=canal (Extra account created just now)
canal.instance.tsdb.dbPassword=canal
canal.instance.dbUsername=root (your main account storing database "review")
canal.instance.dbPassword=root

you can also set the topic name of kafka, for examle, put the message from canal(listening "review") to kafka, and set the topic name such as example:

canal.mq.dynamicTopic=example:review\\..*

then execute:

vi canal-server/conf/canal.properties

modify the following settings and save, then canal is able to push changes to kafka:

serverMode:kafka
kafka.bootstrap.servers = host.docker.internal:29092 (your kafka is deployed in docker)

Check configs/config.yaml under each service folder (like review-service/configs/config.yaml):

• You can change the ports of http and grpc service.
• Check the address of your MySQL.
• Keep consul and elasticsearch's address same with containers in Docker.

Execute the following command in the root directory of each folder:

kratos run

• review-job reads from kafka and writes into elasticsearch.
• review-service register all remote process calls to consul
• review-b/review-o discover remote process calls from consul
• changes in Mysql tables (caused by http or rpc calls) will be captured by canal and pushed to kafka (if your setting is right in above steps).

• check if the service is available with postman or swagger editor
• see routes and parameters in openapi.yaml under each root directory, like link.