> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/prism/architecture/modes-of-usage.md).

# Modes of Usage

Prism can be used in two modes: **Library (SDK)** or **Microservice (gRPC)**.

## Library Mode (Recommended)

In this scenario, Prism SDK is directly embedded into your application. This is the recommended mode for most use cases, because it is,

* Simple to integrate and deploy within your existing server and cloud resources
* No additional network hops
* Full type safety at compile time

## Microservice Mode

You may deploy Prism as a standalone service only if you need service isolation due to

* **Independent deployments** - Being able to update Prism without redeploying your main application
* **Fast release cycles** - Decoupling the SDK released from your app server releases, and you wish to update PRism more frequently than you application

Choose this mode only if you need isolation for fast and independent deployments, because this mode comples with additional complxity to handle - such as deployment, privisioning of resources, uptime and monitoring.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/prism/architecture/modes-of-usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
