Free Preview Chapter
Explore AXPEED DB
The Complete Database Textbook
From First Query to In-Database Machine Learning
34Chapters
8Volumes
72Data Types
470×ML Speed
TNZ Soft (Pvt) Limited
www.axpeed.com
Digital Download — $99.90
Read This Chapter Free — Then Decide
Preview Chapter
Your First Hour

AXPEED DB in 60 Minutes

This is one chapter from a 34-chapter book. In the next sixty minutes, you will install AXPEED DB, run your first queries, and see — with your own hands — the features that make this database unlike anything else on the market: eight paradigms in one engine, seven wire protocols, in-database machine learning that runs 470 times faster than exporting data to Python, post-quantum encryption, and performance numbers that beat PostgreSQL on a fraction of the hardware. Everything in this chapter runs on the free OPEN tier. No credit card. No time limit. No feature restrictions.

1  What AXPEED DB Is

AXPEED DB is a multi-paradigm database built from the ground up by TNZ Soft. One binary. One server. Eight ways to use it.

ParadigmWhat It Means
SQL RelationalTables, JOINs, transactions — the foundation of every business system
Document StoreStore and query JSON inside SQL — no separate MongoDB needed
Key-ValueBlazing-fast lookups by key — no separate Redis needed
GraphTraverse relationships with recursive CTEs and CONNECT BY
VectorSimilarity search for AI embeddings — no separate Pinecone needed
Analytics / OLAPWindow functions, ROLLUP, CUBE — data warehouse queries
Time-SeriesForecast, trend, and correlation functions built in
Full-Text SearchNatural language search with ranking — no separate Elasticsearch needed
KEY POINT
Most organisations run 3–5 separate database products to cover these paradigms. AXPEED replaces all of them with one server, one backup, one security model, and one license.

And it speaks seven wire protocols — PostgreSQL, MySQL, Redis, MongoDB, Oracle TNS, SQL Server TDS, and REST — so your existing applications connect without changing their database driver.

2  Install and Connect

# Linux (Debian/Ubuntu)
sudo dpkg -i axpeed-db_1.4.0h_amd64.deb
sudo systemctl start tnzsoldb

# Connect with the SQL shell
tnzsql -h localhost -p 15432 -U admin -d soldb
tnzsql (1.4.0h)
Type "help" for help.

soldb=#

That is it. The database is running. The default port is 15432, the default database is soldb, and the SQL shell is tnzsql.

REMEMBER
AXPEED also runs on Windows 10/11, macOS 12+, Docker, FreeBSD 13+, and Solelid OS. The full book covers all platforms in Chapter 2.

3  Your First Queries

-- Create a table
CREATE TABLE products (
    id       SERIAL PRIMARY KEY,
    name     TEXT NOT NULL,
    price    NUMERIC(10,2),
    category TEXT,
    specs    JSONB            -- JSON data stored alongside SQL columns
);

-- Insert some products
INSERT INTO products (name, price, category, specs) VALUES
('Laptop Pro 15',   189000, 'Electronics', '{"ram":"16GB","storage":"512GB SSD","brand":"TechCo"}'),
('Wireless Mouse',    2500, 'Electronics', '{"brand":"ClickMax","dpi":3200}'),
('Standing Desk',    45000, 'Furniture',   '{"height":"72-120cm","material":"bamboo"}'),
('Ergonomic Chair',  38000, 'Furniture',   '{"weight_limit":"150kg","adjustable":true}'),
('4K Monitor',       62000, 'Electronics', '{"size":"27 inch","panel":"IPS","refresh":"144Hz"}');
-- Standard SQL — works exactly as you expect
SELECT name, price FROM products WHERE price > 40000 ORDER BY price DESC;
 name           |  price
----------------+---------
 Laptop Pro 15  | 189000
 4K Monitor     |  62000
 Standing Desk  |  45000
(3 rows)
-- Aggregate with GROUP BY
SELECT category, COUNT(*) AS items, AVG(price)::NUMERIC(10,0) AS avg_price
FROM products GROUP BY category;
 category    | items | avg_price
-------------+-------+----------
 Electronics |     3 |    84500
 Furniture   |     2 |    41500
(2 rows)

Query JSON Inside SQL

No separate document database needed. AXPEED stores JSONB in binary format with GIN indexing — query it with SQL operators:

-- Find all products by brand "TechCo"
SELECT name, price, specs->>'brand' AS brand
FROM products
WHERE specs->>'brand' = 'TechCo';
 name          |  price  | brand
---------------+---------+--------
 Laptop Pro 15 | 189000  | TechCo
(1 row)
-- Find electronics with specific JSON attributes
SELECT name, specs->>'size' AS screen, specs->>'refresh' AS refresh
FROM products
WHERE category = 'Electronics' AND specs ? 'size';
 name       | screen  | refresh
------------+---------+---------
 4K Monitor | 27 inch | 144Hz
(1 row)

4  The Performance Numbers

These are independently verified benchmarks — AXPEED DB v1.4.0h versus PostgreSQL 16.15, same hardware (Intel Xeon 2.80 GHz, 2 cores, 7.8 GB RAM), same queries, same data:

4.29× faster than PostgreSQL INSERT — 11,307/sec vs 2,636/sec
1.60× faster than PostgreSQL Point SELECT — 13,140/sec vs 8,232/sec
2.6× lower latency INSERT — 0.130 ms vs 0.333 ms
3.16× faster connection Setup — 2.49 ms vs 7.88 ms

And on a single core with 10 million records:

59,362 TPS transactions per second — single core 10 million records · optimised direct primary key access
KEY POINT
These numbers are from a 2-core virtual machine — not a 64-core server farm. AXPEED is built for performance on modest hardware. Chapter 30 of the full book teaches you how to reproduce these benchmarks yourself with pgbench.

5  In-Database Machine Learning — 470× Faster

This is the number that changes the conversation. When an application needs an ML prediction from data in a database, the traditional approach is:

Traditional Python Pipeline — 12,680 ms total
Query DB
8,302 ms
Serialize
1,815 ms
Deserialize
1,401 ms
Convert
1,142 ms
ML algorithm
21 ms

99.8% of the time is moving data. Only 0.2% is actual machine learning.

AXPEED runs the ML function inside the engine, next to the data. No serialization. No transfer. No conversion:

-- Train a model (one time)
CREATE MODEL price_predictor
USING linear_regression
ON (SELECT sqft, bedrooms, bathrooms, age, price FROM houses);

-- Predict — one line of SQL, 27 milliseconds
SELECT address, predict_price(sqft, bedrooms, bathrooms, age) AS predicted
FROM new_listings
ORDER BY predicted DESC;
 address                  | predicted
--------------------------+----------
 45 Clifton Block 5       | 32500000
 12 DHA Phase 6           | 28100000
 Plot 7, Gulshan-e-Iqbal  | 15800000
(3 rows)
470× Python pipeline: 12,680 ms → AXPEED: 27 ms Same data · Same algorithm · Same answer · The data never moves
REAL WORLD
A hospital predicts patient readmission risk. With the Python pipeline, each prediction takes 12 seconds — impossible during a 10-minute discharge consultation. With AXPEED, the same prediction runs in 27 milliseconds. The doctor gets the risk score before the patient stands up. Chapter 25 builds this from scratch.

6  Security That Does Not Exist Elsewhere

CapabilityWhat It DoesWhy It Matters
Dilithium3Post-quantum cryptography — NIST-standardisedData encrypted today remains secure against quantum computers in 2030, 2040, and beyond
Field DNAPer-field tamper detectionProves a value has not been changed since it was written — even by a DBA with superuser access
UKAUninterceptable Key ArchitectureProtects the data itself, not just the channel — even a network-level attacker cannot decrypt
Direct On Chip (DOC)Boots directly on hardware in 68 seconds — no operating systemEliminates the entire category of OS-level attacks: kernel exploits, rootkits, privilege escalation
Contravention LedgerSHA-256 hash-chained immutable audit trailEvery data change is recorded in an unbreakable chain — meets financial regulator requirements
-- Enable Field DNA on a table
CREATE DNA TABLE financial_records (
    txn_id    SERIAL PRIMARY KEY,
    account   TEXT NOT NULL,
    amount    NUMERIC(12,2),
    recorded  TIMESTAMP DEFAULT NOW()
);

INSERT INTO financial_records (account, amount) VALUES ('ACC-1001', 50000);

-- Verify nobody has tampered with the data
SELECT *, VERIFY_DNA(*) AS integrity FROM financial_records;
 txn_id | account  | amount   | recorded            | integrity
--------+----------+----------+---------------------+----------
      1 | ACC-1001 | 50000.00 | 2026-10-24 09:15:03 | VALID
(1 row)

If anyone changes even one digit of amount — even a superuser — VERIFY_DNA(*) returns TAMPERED. No other database provides this at the individual field level.

7  Vector Search — AI-Native

-- Add embeddings to products (from any AI model — OpenAI, Cohere, etc.)
ALTER TABLE products ADD COLUMN embedding VECTOR(3);

UPDATE products SET embedding = '[0.82, 0.15, 0.91]' WHERE name = 'Laptop Pro 15';
UPDATE products SET embedding = '[0.79, 0.18, 0.88]' WHERE name = '4K Monitor';
UPDATE products SET embedding = '[0.12, 0.95, 0.08]' WHERE name = 'Standing Desk';
UPDATE products SET embedding = '[0.15, 0.92, 0.11]' WHERE name = 'Ergonomic Chair';
UPDATE products SET embedding = '[0.75, 0.22, 0.85]' WHERE name = 'Wireless Mouse';

-- "Show me products similar to the Laptop"
SELECT name, price, embedding <=> '[0.82, 0.15, 0.91]' AS distance
FROM products
WHERE name != 'Laptop Pro 15'
ORDER BY distance
LIMIT 3;
 name           | price  | distance
----------------+--------+----------
 4K Monitor     | 62000  | 0.0014
 Wireless Mouse |  2500  | 0.0038
 Ergonomic Chair| 38000  | 0.9412
(3 rows)

The monitor and mouse are close in embedding space — they are similar products. The chair is far away. This is how recommendation engines work. No separate vector database. No data pipeline. One SQL query.

8  Seven Protocols, One Server

Your MySQL application connects to AXPEED on port 3306 and does not know it is talking to a different database. Your Redis client reads from AXPEED's cache. Your REST frontend calls the database directly with HTTP. One server replaces five.

# PostgreSQL client (port 15432)
psql -h axpeed-server -p 15432 -U admin -d soldb

# MySQL client (port 3306)
mysql -h axpeed-server -P 3306 -u admin -p soldb

# Redis client
redis-cli -h axpeed-server

# REST API (any language, any HTTP client)
curl http://axpeed-server:8081/api/query \
  -d '{"sql":"SELECT * FROM products WHERE price > 40000"}'
REAL WORLD
A company runs 12 microservices: 4 written for PostgreSQL, 3 for MySQL, 2 for Redis, 2 for MongoDB, 1 for REST. With any other database, they need 5 different servers, 5 backup strategies, 5 security configurations. With AXPEED: one server, one backup, one security model. Seven doors in.

9  Licensing That Does Not Punish Growth

Most commercial databases charge per processor core. Upgrade your server from 16 cores to 64 cores — your license cost quadruples, even if your application still uses 30 connections.

AXPEED charges per connection. Upgrade hardware whenever you want. The license cost does not change.

TierConnectionsPrice/MonthAll Features
OPEN5FreeYes
STARTER10$299Yes
BUILDER25$999Yes
GROWTH50$2,999Yes
POWER100$9,999Yes + Priority Support
CUSTOMISEDUnlimitedCustomYes + Dedicated Manager

The OPEN tier is free with no expiration and no feature restrictions. Every student, startup, and developer has access to the full engine. If your application outgrows 5 connections, upgrade. Your data stays exactly where it is.

10  What the Full Book Teaches You

This preview showed you 60 minutes of content. The full book has 34 chapters across 8 volumes — a complete database education from first query to production deployment:

Volume I — Foundations
Chapters 1–10: Installation, SQL basics, data types, JOINs, subqueries, CTEs, aggregate and window functions, 200+ built-in functions, JSONB documents
Volume II — Administration
Chapters 11–18: Transactions and ACID, indexes and EXPLAIN ANALYZE, security and encryption, backup and point-in-time recovery, high availability and MultiRaft clustering
Volume III — Programming
Chapters 19–23: SolPL stored procedures with packages, triggers, the 8 programming paradigms (JDBC, ODBC, REST, Python, Node.js, Java, Go, .NET), Field DNA and contravention ledgers
Volume IV — AI & Machine Learning
Chapters 24–26: Vector search and similarity, in-database ML (regression, classification, clustering), TENSOR operations and neural network inference with ONNX
Volume V — Migration
Chapters 27–30: Migration from PostgreSQL, MySQL, and Oracle. X-2 live comparison — 14-day scientific validation methodology
Volume VI — Business & Licensing
Chapters 31–32: The 6 licensing tiers, AXPEED vs The World — complete capability evaluation
Volume VII — High-Performance Loading
Chapter 33: SolPump — bulk data loading at 11,307 INSERT/sec with data integrity verification
Volume VIII — Mobile & Edge Computing
Chapter 34: Android SDK — embedded and remote database on mobile devices, Kotlin examples, offline-first architecture

Every chapter includes: prerequisite review, learning goals, step-by-step examples you run yourself, real-world scenarios, career builder sections with resume lines and interview questions, exercises with full solutions, and problems rated by difficulty.

Running project: Across 25 build steps, you construct SolPoint — a complete AI-powered point-of-sale system with relational integrity, JSONB product attributes, full-text search, vector similarity recommendations, demand prediction, stockout alerts, neural network product classification, Field DNA audit trails, backup, replication, and security. One database. Zero external services.

Get the Full Book

34 chapters. 8 volumes. From first query to neural networks.
Everything runs on the free OPEN tier.

$99.90
Digital Download — PDF
Download Full Book
What You Just Saw in 60 Minutes

SQL queries, JSONB document storage, aggregate functions, vector similarity search, in-database machine learning at 470× speed, Field DNA tamper detection, Dilithium3 post-quantum cryptography, Direct On Chip deployment, seven wire protocols, per-connection licensing, and benchmarks that beat PostgreSQL on a 2-core machine.

That was one chapter. There are thirty-three more.