IceFireDB-SQLProxy

IceFireDB-SQLProxy

IceFireDB-SQLProxy is a powerful middleware that facilitates the decentralization of traditional SQL database data. It provides a seamless mechanism to construct a globally distributed storage system with automatic networking capabilities. Commands are automatically synchronized across SQL agents within the network, and the IceFireDB SQL agent writes data directly to MySQL storage.

By leveraging the decentralized middleware network proxy, IceFireDB-SQLProxy enables decentralized data synchronization for MySQL databases, which are commonly used in web2 applications. This makes it an ideal solution for bridging the gap between traditional web2 applications and the emerging web3 architecture.

Key Features

• Decentralized Data Storage: Distribute your MySQL data across multiple nodes, ensuring high availability and fault tolerance.
• Automatic Networking: Automatically connect and synchronize SQL agents within the network.
• Web2 to Web3 Transition: Facilitate the migration of traditional web2 applications to a decentralized web3 architecture.
• Easy Integration: Seamlessly integrate with existing MySQL databases without requiring extensive modifications.

How It Works

The IceFireDB-SQLProxy operates by creating a decentralized network of SQL agents that communicate and synchronize data in real-time. Each agent is responsible for writing data to a local MySQL instance, ensuring that the data is replicated across the network. This decentralized approach ensures that your data remains accessible and consistent even in the face of network partitions or node failures.

Getting Started

Prerequisites

• Go (version 1.19 or later)
• MySQL (version 5.6 or later)

Installation

1. Clone the repository:

   git clone https://github.com/IceFireDB/IceFireDB.git
   cd IceFireDB-SQLProxy
   

2. Compile the project:

   make
   

3. Run the proxy:

   ./IceFireDB-SQLProxy -h
   

Configuration

Before running the proxy, ensure that you have configured the necessary MySQL connection settings in the configuration file (config.yaml).

server:
  addr: ":33306" # The port on which the proxy listens, mysql-server, supports direct connection of mysql-client

debug:  # Control to enable debug mode
  enable: true
  port: 17878

# MySQL configuration
mysql:
  addr: "127.0.0.1:3306"
  user: "root"
  password: "password"
  dbname: "exampledb"
  minAlive: 1 # Specifies the minimum number of open connections the pool will attempt to maintain
  maxAlive: 64 # Specifies the maximum number of open connections the pool will attempt to maintain
  maxIdle: 4 # Maximum number of idle connections

# Tenant list
userlist:
  - user: root
    password: rootpassword

# P2P configuration
p2p:
  enable: false
  service_discovery_id: "p2p_sqlproxy_service_test"
  service_command_topic: "p2p_sqlproxy_service_topic_test"
  service_discover_mode: "advertise" # advertise or announce
  node_host_ip: "127.0.0.1" # local ipv4 ip
  node_host_port: 0 # any port

Demo

For a quick demonstration of how IceFireDB-SQLProxy works, check out our demo video.

Application Scenarios

• Decentralized MySQL Storage: Build a decentralized MySQL storage system that can scale horizontally and withstand node failures.
• Web2 to Web3 Transition: Help traditional web2 applications transition to a web3 architecture by enabling decentralized data storage and synchronization.
• High Availability and Fault Tolerance: Ensure that your data remains accessible and consistent even in the face of network disruptions or node failures.

Disclaimers

By using this software, you agree that the author, maintainer, and contributors are not responsible for any risks, costs, or problems you may encounter. If you find a software defect or bug, please submit a patch to help improve it!