The Database Landscape in 2026

PostgreSQL, MySQL, and SQLite have each been around for decades, but their positions in the developer ecosystem have shifted significantly. PostgreSQL has become the default recommendation for new projects. SQLite has undergone a renaissance driven by edge computing, embedded applications, and tools like Litestream and Turso. MySQL remains the most deployed database in the world but has lost mindshare among new projects.

This comparison examines each database through the lens of a developer choosing a database for a new web application. We are not comparing them as enterprise data warehouses or embedded IoT stores — we are evaluating them as the primary datastore for a typical SaaS application.

Architecture Fundamentals

AspectPostgreSQLMySQLSQLite
ModelClient-serverClient-serverEmbedded (in-process)
ConcurrencyMVCCMVCC (InnoDB)WAL mode (readers + 1 writer)
StorageHeap-basedClustered index (InnoDB)B-tree file
Max DB sizeUnlimited (practical)Unlimited (practical)281 TB (theoretical)
ReplicationStreaming, logicalBinary log, group replicationLitestream, LiteFS

The fundamental architectural difference is that SQLite runs inside your application process. There is no separate database server, no TCP connections, no authentication. You open a file and query it. PostgreSQL and MySQL are traditional client-server databases that run as separate processes.

SQL Feature Depth

PostgreSQL implements the SQL standard more completely than any other open-source database. Features that PostgreSQL has had for years are still missing or limited in MySQL:

FeaturePostgreSQLMySQLSQLite
Window functionsFull supportFull support (since 8.0)Full support
CTEs (WITH)Full support, recursiveFull support (since 8.0)Full support
JSON/JSONBNative JSONB with indexingJSON type, limited indexingJSON functions
Full-text searchBuilt-in, configurableBuilt-in (InnoDB)FTS5 extension
Generated columnsStored and virtualStored and virtualStored and virtual
Partial indexesYesNoYes
Array typesYesNoNo
Custom typesYes (enums, composites, domains)Enums onlyNo (type affinity)
UPSERTON CONFLICTON DUPLICATE KEYON CONFLICT

PostgreSQL's JSONB support deserves special mention. You can store JSON documents, index specific paths within them using GIN indexes, and query them with dedicated operators. This makes PostgreSQL viable as a hybrid relational/document database:

-- Store and query JSON in PostgreSQL
CREATE TABLE events (
  id serial PRIMARY KEY,
  data jsonb NOT NULL,
  created_at timestamptz DEFAULT now()
);

CREATE INDEX idx_events_type ON events USING GIN ((data -> 'type'));

SELECT data->>'user_id' as user_id, count(*)
FROM events
WHERE data @> '{"type": "page_view"}'
  AND created_at > now() - interval '7 days'
GROUP BY data->>'user_id'
ORDER BY count(*) DESC
LIMIT 10;

MySQL's JSON support exists but lacks the indexing depth and operator richness of PostgreSQL's JSONB.