> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/server/server-usage/storage-engines/federatedx-storage-engine/differences-between-federatedx-and-federated.md).

# Differences Between FederatedX and Federated

{% hint style="warning" %}
This storage engine has been deprecated.
{% endhint %}

The main differences are:

## New features in FederatedX

* Transactions (beta feature)
* Supports partitions (alpha feature)
* New class structure which allows developers to write connection classes for other RDBMSs without having to modify base classes for FederatedX

## Different behavior

* FederatedX is statically compiled into MariaDB by default.
* When you create a table with FederatedX, the connection are tested. The `CREATE` will fail if MariaDB can't connect to the remote host or if the remote table doesn't exist.

<sub>*This page is licensed: CC BY-SA / Gnu FDL*</sub>

{% @marketo/form formId="4316" %}


---

# 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://mariadb.com/docs/server/server-usage/storage-engines/federatedx-storage-engine/differences-between-federatedx-and-federated.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.