Skip to content

Commit c18343d

Browse files
committed
chore: feedback edits
1 parent b7616b5 commit c18343d

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

apps/www/_alternatives/supabase-vs-firebase.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,9 +58,9 @@ Supabase is open source. Along with the hosted cloud platform, you can also take
5858

5959
[Firebase charges for reads, writes and deletes](https://firebase.google.com/pricing), which can lead to some unpredictability, especially in the early stages of a project when your application is in heavy development. Supabase [charges based on the amount of data stored](https://supabase.com/pricing), with breathing room for unlimited API requests and an unlimited number of Auth users.
6060

61-
### Scaling
61+
### Performance
6262

63-
One scaling limitation you might face when using Firestore - is the 1 document per second limitation on writes. It can be hard to architect around this issue for users who want to be able to sustain high write loads from a single client. Supabase is built on Postgres which is a tested at scale. Every deployment comes with an instance with PgBouncer, a [Postgres connection pooler perfect for use in Serverless computing](https://supabase.com/docs/guides/database/connecting-to-postgres#connection-pool) environments.
63+
We created a benchmarking repo where you can compare the performance of both services in different scenarios. Our most recent results show that [Supabase outperforms Firebase by up to 4x](https://github.com/supabase/benchmarks/issues/8) on number of reads per second, and 3.1x on writes per second.
6464

6565
## How do I migrate from Firebase to Supabase?
6666

apps/www/_alternatives/supabase-vs-heroku-postgres.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -35,29 +35,29 @@ Heroku Postgres and Supabase both offer:
3535
- SLAs and Enterprise-grade support packages
3636
- Direct SSL connections to Postgres
3737
- Postgres Extensions (see [Supabase Extensions](https://supabase.com/docs/guides/database/extensions), [Heroku Extensions](https://devcenter.heroku.com/articles/heroku-postgres-extensions-postgis-full-text-search))
38-
- [Backups and PITR](https://supabase.com/blog/2020/08/02/continuous-postgresql-backup-walg) (not on Heroku’s Hobby tier)
39-
- [Postgres logs](https://supabase.com/docs/guides/platform/logs) (not on Heroku’s Hobby tier)
40-
- Encryption-at-rest (not on Heroku’s Hobby tier)
38+
- [Backups and PITR](https://supabase.com/blog/2020/08/02/continuous-postgresql-backup-walg)
39+
- [Postgres logs](https://supabase.com/docs/guides/platform/logs)
40+
- Encryption-at-rest
4141

4242
## What are the differences?
4343

4444
### Core Features
4545

46-
Both solutions run PostgreSQL, but in a time when Developer Experience matters, there is a lot you can do to improve the speed at which developers can build products faster and with less human resource. These are some of the key differences between Heroku Postgres and Supabase in terms of features:
46+
These are some of the key differences between Heroku Postgres and Supabase in terms of features:
4747

4848
- Supabase is more than just the raw database, it also comes with:
4949
- [Connection pooling](https://supabase.com/docs/guides/database/connecting-to-postgres#connection-pool) so that you won’t run out of connections in a serverless environment.
5050
- [Auto-generated APIs](https://supabase.com/docs/guides/api#rest-api-2) based on your schema, so you can communicate with your database directly from the client.
5151
- [Realtime API](https://supabase.com/docs/reference/dart/subscribe) is useful for when you want to subscribe to changes to your database over websockets.
5252
- [Auth API](https://supabase.com/auth) can be used to leverage Postgres’s Row Level Security model, and control access to sensitive data on a per user, or per group level.
5353
- [Functions](https://supabase.com/edge-functions) can be deployed out to the edge directly from the Supabase CLI, which means you can run sensitive business logic or transformations in a serverless fashion.
54+
- You can also deploy edge functions to Heroku using their [Dynos](https://www.heroku.com/dynos) runtime in conjunction with something like [Fastly](https://www.fastly.com/).
5455
- [File Storage](https://supabase.com/storage) is useful for when your app needs to store large files and folders that aren’t suitable for storing within Postgres itself.
5556
- A spreadsheet-like web interface for building your schemas and inspecting data.
56-
- You can also deploy edge functions to Heroku using their [Dynos](https://www.heroku.com/dynos) runtime in conjunction with something like [Fastly](https://www.fastly.com/).
5757

5858
### Pricing
5959

60-
Simple and predictable pricing are key. The two services price quite differently, the key differences being:
60+
The two services price quite differently, the key differences being:
6161

6262
- [Supabase pricing is based around usage](https://supabase.com/pricing), so you only pay for what you use.
6363
- Heroku prices based on a tier model with [37 plans to choose from](https://elements.heroku.com/addons/heroku-postgresql#pricing).

0 commit comments

Comments
 (0)