Regarding how PlanetScale could be improved, especially considering my experience so far, if it were possible to handle the lagging problem, I suppose it is something that cannot really be changed besides hosting it in other places. The limits of the technology itself are a consideration. I suppose there is not much to do about that. I think it is all fine overall. The features are pretty complete. Are there things that I may not be using? Of course. Overall it looks good. Regarding needed improvements, I have not touched much on the advanced features. We are just using it for essentially basic parts and it works as intended. Nothing more comes to mind.
I would like PlanetScale to have a feature where the database can be accessed in the cloud with a link, allowing for a more user-friendly interface compared to the terminal. This would make it easier to view, create, and manage tables without needing to access the terminal.
We encountered some initial issues during the product deployment, which required me to search for solutions on forums. To minimize the need for external searches, it would be beneficial if the platform could provide more comprehensive documentation or direct solutions for common issues.
The main thing I didn't like about PlanetScale was that we couldn't run analytical queries on it. They bill based on the number of rows read, so even a simple count query could easily use up our allocated resources. Apart from that, I actually loved it. It's based on MySQL, so it doesn't have foreign key constraints or cascades. We have to delete manually or use an ORM. As it's based on MySQL, we can use log posters for complex queries, but it only supports MySQL. I feel like Postgres is more useful for custom or complex queries.
PlanetScale offers seamless database management for Postgres and MySQL with features tailored for modern development environments, enabling enhanced project operations through efficient integration and ease of use.
PlanetScale is designed to support modern developer workflows through features like PgBouncer connection pooling and constant availability, making it ideal for serverless applications. Its integration with tools like Cloudflare and DrizzleORM enhances the developer experience,...
Regarding how PlanetScale could be improved, especially considering my experience so far, if it were possible to handle the lagging problem, I suppose it is something that cannot really be changed besides hosting it in other places. The limits of the technology itself are a consideration. I suppose there is not much to do about that. I think it is all fine overall. The features are pretty complete. Are there things that I may not be using? Of course. Overall it looks good. Regarding needed improvements, I have not touched much on the advanced features. We are just using it for essentially basic parts and it works as intended. Nothing more comes to mind.
I would like PlanetScale to have a feature where the database can be accessed in the cloud with a link, allowing for a more user-friendly interface compared to the terminal. This would make it easier to view, create, and manage tables without needing to access the terminal.
We encountered some initial issues during the product deployment, which required me to search for solutions on forums. To minimize the need for external searches, it would be beneficial if the platform could provide more comprehensive documentation or direct solutions for common issues.
The main thing I didn't like about PlanetScale was that we couldn't run analytical queries on it. They bill based on the number of rows read, so even a simple count query could easily use up our allocated resources. Apart from that, I actually loved it. It's based on MySQL, so it doesn't have foreign key constraints or cascades. We have to delete manually or use an ORM. As it's based on MySQL, we can use log posters for complex queries, but it only supports MySQL. I feel like Postgres is more useful for custom or complex queries.