Managed vs Serverless, SQL explained - #3111
Conversation
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Sites support three domain rule types: Active deployment, Git branch, and Redirect |
Greptile SummaryThis PR adds two new SEO blog posts and their cover assets.
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (4): Last reviewed commit: "Apply suggestion from @aishwaripahwa12" | Re-trigger Greptile |
|
|
||
| A SQL query reads like a sentence. To get every column for every user, you write: | ||
|
|
||
| ```sql |
There was a problem hiding this comment.
Unsupported SQL Fence Language
When this post renders, the sql fence language is passed to the existing code highlighter, but SQL is not registered in the supported language set. The examples can render without the expected syntax highlighting and may emit highlighter warnings on a SQL-focused article.
Prompt To Fix With AI
This is a comment left during a code review.
Path: src/routes/blog/post/sql-explained-how-developers-query-databases/+page.markdoc
Line: 59
Comment:
**Unsupported SQL Fence Language**
When this post renders, the `sql` fence language is passed to the existing code highlighter, but SQL is not registered in the supported language set. The examples can render without the expected syntax highlighting and may emit highlighter warnings on a SQL-focused article.
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| @@ -0,0 +1,125 @@ | |||
| --- | |||
| layout: post | |||
| title: "Managed Postgres vs. serverless databases: Which one should developers choose?" | |||
There was a problem hiding this comment.
This needs to be dedicated vs serverless
Serverless database offerings have to be managed by the cloud provider so this piece doesn't make sense
| # Start querying your data with Appwrite Databases | ||
|
|
||
| Understanding SQL gives you a mental model that applies to nearly every database you will ever touch: describe the data you want, and let the engine do the work. Whether you write raw queries or use a Query API, the core ideas of filtering, joining, aggregating, and transactions stay the same. | ||
|
|
||
| If you want that querying power without managing a database server yourself, [Appwrite Databases](/docs/products/databases) gives you filtering, sorting, and pagination through a clean [Query API](/docs/products/databases/queries), backed by a relational engine and wrapped in permissions and realtime. It is a fast way to put everything in this post into practice. |
There was a problem hiding this comment.
This needs to be about our native databases, not our shared database APIs.
…which-one-should-developers-choose/+page.markdoc
| answer: Some serverless databases can have cold starts when compute scales to zero and needs to resume. This can add latency to the first query after an idle period, so it matters for latency-sensitive applications. | ||
| - question: Is serverless Postgres the same as managed Postgres? | ||
| answer: No. Serverless Postgres is still managed, but it uses automatic scaling and usage-based billing. Traditional managed Postgres runs as a provisioned, always-on instance with fixed capacity. | ||
| - question: Is managed Postgres better than a serverless database? |
There was a problem hiding this comment.
| - question: Is managed Postgres better than a serverless database? | |
| - question: Is managed Postgres better than a serverless database? |


Latest SEO blogs