---
title: Query Configuration
---

Queries can be configured for service routing and endpoint behavior in both React and non-React environments.

## Microservice Routing

Per query:

```typescript
query.setMicroservice('inventory-service');
```

In React applications, configure this globally with `<Arc microservice="..." />`.

## API Base Path

Per query:

```typescript
query.setApiBasePath('/api/v1');
```

In React applications, set this globally with `<Arc apiBasePath="..." />`.

## Observable Query Transport (`queryDirectMode`)

By default, observable queries use centralized hub endpoints. Set `Globals.queryDirectMode = true` to bypass the hub and connect directly per query.

```typescript
import { Globals } from '@cratis/arc';

Globals.queryDirectMode = true;
```

| Value | Description |
|-------|-------------|
| `false` (default) | Route through `/.cratis/queries/sse` or `/.cratis/queries/ws`. |
| `true` | Connect directly to each observable query WebSocket URL. |

In React, this is usually configured through `<Arc queryDirectMode={...} />`. See [React query integration](/arc/frontend/react/queries/).

## Query Cache Retention (`queryCacheRetentionMs`)

Controls how long (in milliseconds) the query cache keeps an entry alive after the last subscriber releases it. The default is `30 000` ms (30 seconds).

```typescript
import { Globals } from '@cratis/arc';

// Keep cached data for 60 seconds after the last subscriber unmounts.
Globals.queryCacheRetentionMs = 60_000;

// Restore immediate eviction.
Globals.queryCacheRetentionMs = 0;
```

In React applications, set this through `<Arc queryCacheRetentionMs={...} />` instead of modifying `Globals` directly. See [React query configuration](/arc/frontend/react/queries/configuration/).

## See Also

- [Observable Queries](/arc/frontend/react/queries/observable-queries/)
- [Observable Query Multiplexing](/arc/frontend/react/queries/observable-query-multiplexing/)