- Introduction
- Usage
- Contributing Code
This is a demo project based on GCP Online Boutique with added support for REST and Thrift APIs. It is designed to be used during cloud-native development for testing across different APIs–REST, gRPC, and Thrift. It is extensible in support of future functionality (e.g. GraphQL).
- Use as a test project for developing cloud-native dev tools.
- Learn how to implement Thrift (and REST) support for an existing project.
Implemented by the Skyramp team.
For each microservice in the repo, REST and Thrift implementations open up separate ports to listen to the corresponding traffic. Implementations are in the rest.go and thrift.go files in the top-level directory for each service.
Default ports for REST and Thrift are hardcoded in the main.go file in each service directory. For example, the carts microservice has the following ports defined:
const (
serverCrt = "server.crt"
serverKey = "server.key"
defaultThriftPort = "50000"
defaultRestPort = "60000"
)
- docker
- curl (required for REST)
- jq (optional)
- kubectl (optional)
git clone https://github.com/letsramp/sample-microservices.git
cd sample-microservices/src
Images for sample-microservices are already available in a publically accessible registry. To use your own registry, follow these steps.
docker compose build
Update the host path/s in the docke-compose.yaml file to point to your own docker registry. Push images by running:
docker compose push
Deploy Online Boutique by running the following command:
docker compose up
Now, familiarize yourself with the application by navigating to https://127.0.0.1:8080 on your browser.
📝 NOTE: If you are using Docker Desktop, you can look at the logs for
cart serviceto see that we've opened up separate ports for gRPC(7070), REST(60000), and Thrift(50000) traffice to the service.
To demonstrate the REST and Thrift implementations, we've created simple clients (src/clients) for the "add to cart" scenario for each of the APIs. The client code is accessible from the clients container in the cluster.
To connect to the clients container, run the following command in your terminal:
docker compose exec -it clients ash
Optionally, you can download and install Docker Desktop to follow along.
If you are using Docker Desktop, click on the clients_1 container and go to the CLI from there.
- In the
clientscontainer, navigate to the grpc/golang folder and download the requiredgomodules.
cd /grpc/golang
go mod download
- In the
addCart.gofile, you will notice that we open a connection to port 7070 ofcartmicroservice which listens to grpc traffic.
conn, err := grpc.Dial("cartservice:7070", grpc.WithInsecure())
- Run the code in the file to add an item to the cart.
go run ./cmd/cart
Expected result
Successfully added the item to the cart.
Having seen how to successfully add an item to the cart with a gRPC client calling the gRPC endpoint, we can see how to do the same through the REST and Thrift endpoints.
Since cURL is already installed in the clients container, you can issue a request directly from the CLI of the container to add an item to the cart.
curl -X 'POST' 'https://cartservice:60000/cart/user_id/abcde' \
-H 'accept: application/json' \
-H 'content-type: application/json' \
-d '{
"product_id": "OLJCESPC7Z",
"quantity": 1
}'
Again, notice that the request is being sent to port 60000 of cart microservice which listens to REST traffic.
Result
{"success":"200 OK"}
- In the
clientscontainer, navigate to the thrift/golang folder and download the requiredgomodules for the Thrift client.
Setup
cd /thrift/golang
go mod download
- In the
addCart.gofile, you will notice that we open a connection to port 50000 ofcartmicroservice which listens to Thrift traffic.
clientAddr := "cartservice:50000"
- Now, run the code in the file to add an item to the cart.
go run ./cmd/cart
Result:
"Successfully added the item to the cart."
You can now fetch the contents of the cart using REST API to see that a total of 3 items were added (one using each supported API).
curl -X 'GET' \
'https://cartservice:60000/cart/user_id/abcde' \
-H 'accept: application/json'
Result:
{"user_id":"abcde","items":[{"product_id":"OLJCESPC7Z","quantity":3}]}
This repo contains a number of test scenarios used for demo purposes. These test scenarios are located under the skyramp folder in grpc-demo, rest-demo, and thrift-demo. The test scenarios can be run using the Skyramp client. Visit the Skyramp Docs for instructions on installing the Skyramp client.
Once the microservices have been deployed to a cluster, you can run the demo tests with the Skyramp CLI. See the Walkthrough in the Skyramp Docs for one method of deployment with Skyramp Deployer.
To run the tests for the REST demo, as an example, navigate to the rest-demo folder in a terminal:
cd sample-microservices/skyramp/rest-demoYou can see the existing test description files under tests:
checkout-test.yaml
test-load.yaml
test-trace-bOl4.yamlRunning the checkout-test test with Skyramp Tester...
skyramp tester checkout-test -n test-rest-demoWill produce output similar to this:
Starting tests
Tester finished
Test [REST] Checkout system testcase------
[Status: finished] [Started at: 2023-11-04 16:41:21 PDT] [End: 2023-11-04 16:41:22 PDT] [Duration: 1s]
- pattern0.scenario1
[Status: finished] [Started at: 2023-11-04 16:41:22 PDT] [Duration: 0s]
- pattern0.scenario1.0.addCartRequest
[Status: finished] [Started at: 2023-11-04 16:41:22 PDT] [Duration: 0s]
Executed: {"success":"200 OK"}
- pattern0.scenario1.1.getCartRequest
[Status: finished] [Started at: 2023-11-04 16:41:22 PDT] [Duration: 0s]
Executed: {"user_id":"abcde","items":[{"product_id":"OLJCESPC7Z","quantity":2}]}
- pattern0.scenario1.2.assert
[Status: finished] [Started at: N/A]
Assert: requests.getCartRequest.res.user_id == "abcde"
Passed: true
- pattern0.scenario1.3.checkoutRequest
[Status: finished] [Started at: 2023-11-04 16:41:22 PDT] [Duration: 0s]
Executed: {"order_id":"1cae99ba-f22e-42cd-8b4d-79160ef3ae72","shipping_tracking_id":"2c287fac-104a-4a4b-a3fc-32f1ec3a7495","shipping_cost":{"currency_code":"USD","units":10,"nanos":100},"shipping_address":{"street_address":"1600 Amp street","city":"Mountain View","state":"CA","country":"USA"},"items":[{"item":{"product_id":"OLJCESPC7Z","quantity":2}}]}
- pattern0.scenario1.4.assert
[Status: finished] [Started at: N/A]
Assert: requests.checkoutRequest.res.items[0].item.product_id == "OLJCESPC7Z"
Passed: trueTest files can be created manually or generated using the skyramp generate command. The test files can then be edited and customized for your specific testing requirements. For more information on creating or generating tests, see the Skyramp Docs covering the Test Description and the specific CLI command - tester generate.
Notice from the Skyramp docs that there are a number of possible options for generating tests. Tests can be generated using an API schema definition with OpenAPI or Protocol Buffers as well as with telemetry trace data from an observability provider like Pixie.
You will see in the skyramp/rest-demo folder in this repo that there are openapi and trace folders containing example input files for generating tests. The test-trace-bOl4.yaml demo test description was generated from trace data. Here are a few examples to illustrate test generation options with various inputs:
skyramp tester generate \
--trace-file trace/trace.jsonskyramp tester generate \
--protocol openapi \
--api-schema openapi/demo.yaml \
--alias test-rest-demo \
--port 60000skyramp tester generate \
--telemetry-provider pixie \
--cluster-id cluster-id \
--namespace namespace \
--start-time "-5m" skyramp tester generate grpc \
--api-schema file.proto \
--alias namespace \
--port port \
--service servicePRs are welcome!
This project follows the CNCF Code of Conduct .