Knowledge Hub
Compare the features of the Serverless Database to help you choose the right one for your needs.
Feature | ![]() | ![]() | ![]() | |
---|---|---|---|---|
Infrastructure, Underlying technology Cloud Infrastructure, database system and underlying egine | Nodejs, Google Cloud, Scala | AWS infrastructure | Supabase infrastructure, PostgreSQL, S3 compatible storage object | |
Serverless Support Serverless and Edge computing support | ||||
API | REST API | @aws-sdk/client-dynamodb, native support for Vercel Edge, Cloudflare Workers | Deno Edge Function | |
Edge Functions Serverless functions that run closer to the user, reducing latency and improving performance. | Cloud functions | Runs over HTTPS protocol, compatible with Edge runtimes.Native multi-regional edge support. You can define regions for each table | Supabase infrastructure | |
Developer Experience | ||||
Database type | OLTP, OLAP | OLTP | OLTP | |
Data model Databases store data in models, such as Relational, Columnar or Document based | Document based, NoSQL | key-value, NoSQL | Relational, SQL | |
CLI Command Line Interface tools that allow developers to perform tasks and manage the tool via the command line. | Firebase CLI | AWS CLI tools | supabase | |
Languages, APIs The languages supporting the database and API interface for inter-process communication | JavaScript, Swift, Kotlin, Java, C++, Objective-C | Supported by majority of languages including Node.js, Python, Java, Go, C#, C++ | TypeScript, JavaScript, supabase-js SDK, Flutter, React Native, React | |
Query language Supported query language such as SQL, MQL, PartiQL, | JSON | PartiQL (JSON like syntax) | SQL, PostgreSQL | |
ACID compliant ACID is a set of properties of database transactions intended to guarantee data validity despite errors, power failures, and other mishaps | ACID compliant | ACID compliant | ||
Self-hosting Support for self-hosted Database instance | Doesn't have support | Doesn't have support, Only for local development | Docker support | |
Backups | Point-in-time recovery (PITR) provides continuous backups of your DynamoDB table data. When enabled, DynamoDB maintains incremental backups of your table for the last 35 days until you explicitly turn it off. | Daily basis (Included in Free tier), PITR for paid users | ||
Security & Compliance Offerings | ||||
SOC2 Service Organization Control 2 compliance for managing customer data. | Apart from App indexing | |||
Multi-factor authentication Support of the cloud-histed database for multi-factor authentication | ||||
Encryption Cryptographic security at rest and on transportation level | HTTPS, TLS | All your data in DynamoDB is encrypted in transit, HTTPS, TLS | AES 256 Encryption, TLS v1.2 | |
SSO | SAML-based SSO solution | |||
Monitoring and analytics | ||||
Log retention Query log retention usually keeps lofs of operations for debugging and replication purposes | Document level history 30 days retention | AWS CloudTrail for operation logs | By default disabled, can be enabled with pgAudit extension | |
Statistics Tools and APIs for analysing and monitoring of Database performance | Web based monitoring tools | Amazon CloudWatch to monitor performance metrics | Web dashboard, provides Prometheus-compatible metrics endpoints to gather health insights | |
Scalability | ||||
Replication and Partitioning | Region groups | "Global tables", Multi-region replication | read replicas in early preview |