hipstershop should have at least one http service apart from frontend.

At present only frontend is the http1.1 service. This is not a typical customer. We expect customers to have many http1.1 and a few grpc or 50-50. This application is widely used in service mesh demos.

1. Convert one service to http
2. Or give the ability to deploy a grpc service as http and update clients accordingly.

[prune998]

We forked the (old) hipstershop and put some huge changes in it. Like supporting Zipking and Jaeger. I also re-wrote the adservice in Go, and added cool features like:

• it’s talking HTTP
• you can add a start delay to simulate a slow starting service (only the /healthz endpoint reflect that)
• you can add a delay to the answer to simulate a busy service
• you can add a number of error 500 to return before returning the real payload

Of course, I had to update the frontend to change the call from GRPC to HTTP… At least you can base the PR on my changes… BTW, I also cloned/updated the frontend as a apiservice, which returns JSON instead of HTML… this is to demo traffic routing between regular calls on / and API calls on /api

Check it out at https://github.com/tetratelabs/microservices-demo

[askmeegs]

Also want to add that Bank of Anthos is all HTTP-based, six services.

Understanding that a major architectural update for OnlineBoutique is not in the roadmap right now, I’m going to close this issue.