Saphira Linux databaseDragon

Relational databases on infrastructure you control: choose SQLite, MariaDB or PostgreSQL, understand the access you need, and keep your data where it belongs.

In testing, functionality present — helpers missing

Three useful choices

Saphira provides SQLite, MariaDB and PostgreSQL. They are different tools for different workloads, not competitors that must replace one another. Start with the application and where it runs, then choose the database that fits it.

SQLite: relational data on one host

SQLite is a real relational database embedded in an application or local tool. It keeps the database in a file and does not require a separate database server. That makes it an excellent fit for small applications, internal utilities, agent memory, application state, development and single-host workloads.

NoteSQLite is not a toy database. It is often exactly the right answer when an application needs structured relational data but does not need remote database-server access.

MariaDB: the conventional application server

MariaDB is a natural fit for Saphira's web and application stack. It serves websites, PHP applications, Node.js applications, content systems, business applications, APIs and services that need a conventional SQL database server. An application may be on the same machine or, where intentionally configured, on another server.

Create the website with webDragon; give the application the database it needs with databaseDragon. The relationship is useful, but not exclusive: a MariaDB server can serve many kinds of software beyond websites.

PostgreSQL: another mature server choice

PostgreSQL is also part of Saphira's supported relational database story. It is a mature database server for applications that choose PostgreSQL or make use of its particular SQL and data capabilities. There is no need for a MariaDB-versus-PostgreSQL argument here: Saphira provides the choice.