GroupeZ Docs
AddonszAuctionHouseRedis

zAuctionHouse Redis

Connect multiple servers with zAuctionHouse Redis addon

zAuctionHouse has been designed from the ground up with performance and scalability in mind. Whether you're running a small survival server or a large network like DonutSMP, zAuctionHouse is built to handle high traffic and multiple servers seamlessly.

zAuctionHouse Redis Addon

To connect multiple servers and synchronize your auction house across your entire network, you need the zAuctionHouse Redis addon.

Buy on GroupeZ - 15€Buy on BuiltByBit - 20.99$

Features

  • Real-time synchronization - Items listed on one server appear instantly on all others
  • Distributed locking - Prevents double purchases and race conditions
  • Event propagation - All auction events (listing, purchase, removal) are synchronized
  • Cache invalidation - Ensures all servers have up-to-date data
  • High performance - Minimal latency impact on your servers

Why Redis?

Redis is an in-memory data structure store that provides extremely fast read and write operations. It is particularly well-suited for scenarios where multiple servers need to share and synchronize data in real time.

Performance Comparison

SolutionSpeedReal-time SyncData Consistency
RedisExtremely fast (in-memory)YesExcellent
SQL DatabaseSlower (disk-based)NoGood
BungeeCord/VelocityN/ANoN/A

Why not SQL?

Unlike traditional SQL databases, which are disk-based and can introduce significant latency when handling frequent read and write operations, Redis operates directly in memory. This makes it ideal for applications that require high-performance, low-latency access to shared data.

Using SQL to synchronize multiple servers is not efficient for an auction house. SQL databases are designed for persistent storage, meaning each read or write operation involves disk access. This becomes a bottleneck when dealing with frequent updates from multiple servers. Additionally, SQL doesn't provide the real-time synchronization that an auction house requires, leading to delays and potential data conflicts.

zAuctionHouse still uses SQL (MySQL/MariaDB/PostgreSQL) for persistent data storage. Redis is used as a cache layer for real-time synchronization between servers.

Why not BungeeCord/Velocity messaging?

BungeeCord and Velocity are proxy solutions that facilitate communication between Minecraft servers, but they are not designed for data synchronization. While they can pass messages between servers, they lack the capability to efficiently manage shared data like auction items.

Redis, on the other hand, is designed for exactly this purpose: providing a shared, fast-access cache that multiple servers can use to ensure data consistency.

Key Benefits of Redis

  1. In-memory storage - Data is stored in RAM for instant access
  2. Pub/Sub messaging - Real-time event propagation across all servers
  3. Atomic operations - Prevents race conditions and data corruption
  4. Distributed locking - Ensures only one server can modify an item at a time
  5. Scalability - Handles thousands of operations per second

Architecture

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│  Server 1   │     │  Server 2   │     │  Server 3   │
│zAuctionHouse│     │zAuctionHouse│     │zAuctionHouse│
│+ Redis Addon│     │+ Redis Addon│     │+ Redis Addon│
└──────┬──────┘     └──────┬──────┘     └──────┬──────┘
       │                   │                   │
       └───────────────────┼───────────────────┘
                           │
                    ┌──────▼──────┐
                    │    Redis    │
                    │   Server    │
                    └──────┬──────┘
                           │
                    ┌──────▼──────┐
                    │MySQL/MariaDB│
                    │ /PostgreSQL │
                    └─────────────┘

How it works:

  1. Player lists an item on Server 1
  2. Item is saved to the shared SQL database (MySQL, MariaDB or PostgreSQL)
  3. Redis publishes an event to all servers
  4. Servers 2 and 3 receive the event and update their cache
  5. Players on all servers see the item instantly

Next Steps

On this page

GroupeZ MCP

Documentation in your AI

MCP lets your AI search GroupeZ documentation and read current examples to help you configure your plugins.

Read-only · No documentation API key needed

1. Copy the server URL

Transport: HTTP (Streamable HTTP). Authentication: none. Your tool uses its own model and subscription limits.

  1. Open Plugins in ChatGPT on the web, then + → Add custom MCP server.
  2. Name it ‘GroupeZ Documentation’, paste the URL above and choose ‘No authentication’. Create and install the plugin.
  3. In a conversation, type @ and select the plugin before asking. If needed, enable search, get_page and list_pages in its settings.
Official setup guide

3. Ask a question

Use GroupeZ MCP to help me create a zMenu inventory. Search relevant pages, read the examples and cite your sources.
Other clients and troubleshooting

For clients using mcpServers, adapt this example to their format:

{
  "mcpServers": {
    "groupez-docs": {
      "url": ""
    }
  }
}

Available tools are search, get_page and list_pages. Refresh the connector’s tools after updates. If your AI cannot access them, check that the connector is enabled in the conversation and your account allows custom MCP servers. Opening the URL in a browser is not an MCP test.