> For the complete documentation index, see [llms.txt](https://docs.dyrector.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dyrector.io/features/templates/google-microservices-demo.md).

# Google Microservices Demo

[**Google Microservices Demo**](https://github.com/GoogleCloudPlatform/microservices-demo) **is used to how to build and deploy microservices-based applications using Google Cloud Provider (GCP). Google Microservices Demo allows users to demonstrate use of technologies like Kubernetes/GKE, Istio, Stackdriver, gRPC and OpenCensus. Users can quickly set Google Microservices Demo up on your infrastructure.**

{% hint style="info" %}
All images are available with `0.4.1` tag in the template.
{% endhint %}

After the Node where you'd like to run Google Microservices Demo is [**registered**](/tutorials/register-your-node.md), you can set it up by following the steps of deployments as documented [**here**](/tutorials/deploy-your-product.md).

Once the deployment is successful, Google Microservices Demo is ready to use at  [**localhost:65534**](http://localhost:65534) by default, as seen below.

<figure><img src="/files/5dT1JGdYMjzkF5LToKbQ" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dyrector.io/features/templates/google-microservices-demo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.