4 ms·
I just started a small hobby project and selected supabase for my db provider. Anyone with experience in both Supa and PlanetScale care to comment about the dif
by edmundsauto 4y ago
I just started a small hobby project and selected supabase for my db provider. Anyone with experience in both Supa and PlanetScale care to comment about the differences?
To me, it looks like supabase is designed to take full advantage of postgres features. plpgsql triggers + RLS + clientside auth + streaming changes to subscribers (including via web hooks) are my favorite features. (They also have js edge functions, but I use lambda instead b/c I prefer python)
Supabase feels like the scrappy company with amazing focus, akin to an early MailChimp (circa 2007). PlanetBase feels more like early Snowflake - massive scale, focus on performance, can match anything feature-by-feature. One is a master of their craft, the other is a gorilla at scale.
Curious what others think. I haven't used PlanetBase extensively so don't have much to go on except their marketing.
- Jarwain 4y agoThat sounds about right from my understanding. Supabase was made as an alternative to firebase, acting as a data layer with a lot of features simplifying application development. Planet Base feels like Snowflake, or some aspects of fly.io, or timescale's managed cloud offering; their focus is on the core database tech and delivering that in a scalable manner.
- greg-m 4y agoReadySet (readyset.io) supports the same style of caching and works with Supabase, if you want to check us out :) I have a few extra cloud invites: greg@readyset.io
- edmundsauto 4y agoMuch appreciated, I will check you out for my next project. Right now I'm not able to migrate as I'm trying to get an MVP up and running and have spent a few days deeply integrating w/ Supabase. What are your core value prop differences between your service and sb? Just curious how I should think about your offering compared to what I'm familiar with.
- greg-m 4y agoWe work with supabase - so your DB still deploys out to them, but we cache queries in memory so they're significantly lower latency. Since we're offloading reads, we also help handling traffic spikes, lower costs, etc.
- edmundsauto 4y agoAh gotcha, that makes sense. My little hobby app has no need for any perf optimizations and I’m trying to minimize the surface area of technologies I incorporate. I’ll keep you in mind for anything that does require performance! Currently I’m doing about 5 requests per day to the db layer, all from my dogfooding. With a very simple data model.