# Db and Annotations

*JTX* supports multiple resource types, but its most efficient with single resource type, such as relational database. Therefore, there is whole layer build on top of generic *JTX* classes that serves just to simplify use and usage of transaction over databases.

### Declarative transactions

But that is not all. Transactions, in general, are a perfect example of scattered logic, that can be encapsulated via aspects. With help of *Proxetta*, *JTX* can be applied on methods that are annotated with `@Transaction` annotation.

#### Custom transactions

In most applications we would have only two types of transactions: one that only read and one that allows writing data. `@Transaction` annotation by default matches read-only transactions, meaning that on every place where read-write transaction is needed, user have to write this with annotation elements.

To reduce this boilerplate code, it is possible to define custom annotation that takes different default values.


---

# Agent Instructions: 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:

```
GET https://db.jodd.org/jtx/db-and-annotations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.