I have just begun playing with Supabase and have a habit of running `brew upgrade` several times per week. It bugs me that the Supabase CLI is updated every single time I run `brew upgrade`. I suspect that if I were to run `brew upgrade` twice a day, it would probably still update every single time. It makes me feel like I'm trying to swing a bat around, except it's made of water.
Migrating from Supabase
101–110 of 136 posts
Re: Migrating from Supabase
#102Great read. Similar to my experience with Hasura. Migrations we’re better there but the row level security was a nightmare. Went to just a custom node backend with prisma and it’s a dream. No more writing tons of json rules and multiple views just to not query the email field. Seems like these types of services are good for basic large scale crud applications, probably why you have Hasura pivoting to enterprise. The…
Had a similar experience with Hasura. They have done some amazing things leveraging Postgres and GraphQL. But there were just too many things that got really questionable. Things like migrations becoming inconsistent with metadata, schema lock in, poor ability to do rate limiting, having to use stored procedures for everything, weird SQL that had performance issues, unexplained row level locking, and so on. Local dev…
100%. Same things we ran into. Definitely a trap.
Re: Migrating from Supabase
#103What was most shocking to me was that it took a week to migrate 40GB.
I once migrated 1TB from RDS Oracle to RDS Aurora MySQL in 6 hours. I'm not familiar with Supabase, maybe there's a lot more to the data migration process?
Re: Migrating from Supabase
#104Nice read. I run 5-6 projects on Supabase currently. I have also run into the local development / migration obstacles. It's otherwise been pretty great for our needs
The CLI could use some love for sure. I think the migrations experience is also where I’ve felt the most pain. I will say, the CLI very heavily assumes that you are using the cloud product as the remote, which I guess is absolutely intentional (it’s a path to get users onto the product) but it was kind of annoying to figure that out halfway into a POC like I did. Don’t go in expecting you can point the CLI at some se…
Hello, I work on CLI full time. Things have certainly improved over the last few months on using this tool for migrating self-hosted databases.
Currently all supabase db and migration commands support --db-url flag [1] which allows you to point the CLI to any Postgres database by a connection string.
If there's any use case I missed, please feel free to open a GitHub issue and I will look into it promptly.
Re: Migrating from Supabase
#105Earlier quoted context omitted.
I don't use supabase, but am a big postgres fan: > that stuff in unmaintainable Wrong. Version your functions and use something like liquibase to apply migrations.
Way less friendly than writing code IMO
Developer friendly matters early on, performance and security friendly matters at scale
Re: Migrating from Supabase
#106Wondering if the supabase CEO or any customers here can discuss scale. What “size” applications are doing really well on supabase? Are there any customers with TBs (or more) of data? What sort of performance are they achieving? Any customers with previous experience at a larger scale that are now using supabase and similar or larger scale, how are things going? What’s the average development team size of customers?
Re: Migrating from Supabase
#107Earlier quoted context omitted.
And handwrite xml? No thanks. Again, if I wanted to do any of this management myself, I wouldn't be using a PaaS.
You don't have to use the xml format if you don't want to. Not sure why you wouldn't want to, since the xsd enables autocompletion in your IDE which makes it the most practical format of all. Anyway, YAML and SQL format are a thing https://docs.liquibase.com/concepts/changelogs/yaml-format.h... https://docs.liquibase.com/concepts/changelogs/sql-format.ht...
Or Bytebase if you want a more sophisticated GitLab like experience
Re: Migrating from Supabase
#108Earlier quoted context omitted.
I cannot be the only person here (are there any people left?) that wishes that the comments section does not evolve to LLM summaries of articles.
For me it's the opposite. You've got the CEO speaking corporate platitudes trying to defend himself in the comments by removing focus on the actual issues at hand. LLM helped summarize the issues at hand.
None of what the ceo posted was corporate platitude. This sort of post actively lowers the quality of HN comments.
Re: Migrating from Supabase
#109Having worked on a Baas type offering, this is all very familiar. Over the years, I've come to believe the approach of trying define a service layer with these magic abstractions is fundamentally flawed and will always lead to the problems in this article: poor performance, poor local development experience, no transparency in to what is going on under the hood. They are great for fast proof of concepts, but not sustainable, long term product development.
Re: Migrating from Supabase
#110hey hn, supabase ceo here the Val Town team were kind enough to share this article with me before they released it. Perhaps you know from previous HN threads that we take customer feedback very seriously. Hearing feedback like this is hard. Clearly the team at Val Town wanted Supabase to be great and we didn’t meet their expectations. For me personally, that hurts. A few quick comments 1. Modifying the database in pr…
Really appreciate this response.
Looking at your first link, there's a link to this page which currently resolves to a 404: https://supabase.com/docs/guides/platform/docs/guides/platfo...