Skip to content

SEO Blogs (CRUD, Database sharading, server-side rendering)#3087

Open
aishwaripahwa12 wants to merge 2 commits into
mainfrom
crud-database-sharading-server-side-rendering
Open

SEO Blogs (CRUD, Database sharading, server-side rendering)#3087
aishwaripahwa12 wants to merge 2 commits into
mainfrom
crud-database-sharading-server-side-rendering

Conversation

@aishwaripahwa12

Copy link
Copy Markdown
Contributor

Latest SEO blogs

@appwrite

appwrite Bot commented Jul 7, 2026

Copy link
Copy Markdown

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)
Site Status Logs Preview QR
 website
69d7f2670014e24571ca
Ready Ready View Logs Preview URL QR Code

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
 website
68496a17000f03d62013
Queued Queued View Logs Preview URL QR Code


Tip

Messaging handles push notifications, emails, and SMS through one unified API

@greptile-apps

greptile-apps Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds three new SEO-focused blog posts (what-is-crud-explained, what-is-database-sharding-a-beginners-guide, what-is-server-side-rendering-a-beginners-guide) along with their cover images and corresponding .optimize-cache.json entries. All posts are marked unlisted: true, indicating they are staged for later publication.

  • Each post has valid frontmatter (author, date, cover, category, faqs) and links to correct Appwrite documentation in the Resources section.
  • Cover images are committed as .avif files; cache entries reference .png extensions, which is the established convention in this repo.
  • The duplicate # Conclusion section previously flagged in the sharding post has been resolved in the current revision.

Confidence Score: 5/5

Three new static blog posts and cover images with no logic changes; safe to merge.

All changes are additive content files. Frontmatter is well-formed, author handles are valid, cache entries are present for every new image, and no duplicate content remains in the sharding post.

No files require special attention.

Important Files Changed

Filename Overview
src/routes/blog/post/what-is-crud-explained/+page.markdoc New SEO blog post explaining CRUD operations; frontmatter, author, cover image, and cache entry are all correct.
src/routes/blog/post/what-is-database-sharding-a-beginners-guide/+page.markdoc New SEO blog post on database sharding; single conclusion section (previously-flagged duplicate was resolved), valid author handle, correct frontmatter.
src/routes/blog/post/what-is-server-side-rendering-a-beginners-guide/+page.markdoc New SEO blog post on server-side rendering; frontmatter, author, cover image, and cache entry are correct.
.optimize-cache.json Adds cache entries for all three new cover images; all new blog images have corresponding entries.

Reviews (2): Last reviewed commit: "Update +page.markdoc" | Re-trigger Greptile

Comment thread src/routes/blog/post/what-is-database-sharding-a-beginners-guide/+page.markdoc Outdated
Comment on lines +97 to +108
# Conclusion

Database sharding splits a large database into smaller shards spread across multiple servers, letting it scale horizontally to handle more data and traffic than any single machine could. The heart of a sharded system is the shard key, which determines how evenly data and load are distributed, and the strategy you choose, such as hash-based or range-based, shapes how your queries perform. Sharding is distinct from partitioning, which can happen on one server, and from replication, which copies data for availability rather than splitting it for scale.

The practical takeaway is that sharding is a powerful but complex tool best reserved for real scaling problems. Exhaust indexing, caching, and replication first, and lean on managed infrastructure so you're not carrying the operational weight of many databases by hand.

# Conclusion

Database sharding splits a large database into smaller shards spread across multiple servers, letting it scale horizontally to handle more data and traffic than any single machine could. The heart of a sharded system is the shard key, which determines how evenly data and load are distributed, and the strategy you choose, such as hash-based or range-based, shapes how your queries perform. Sharding is distinct from partitioning, which can happen on one server, and from replication, which copies data for availability rather than splitting it for scale.

The practical takeaway is that sharding is a powerful but complex tool best reserved for real scaling problems. Exhaust indexing, caching, and replication first, and lean on managed infrastructure so you're not carrying the operational weight of many databases by hand.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two conclusion sections?

Comment on lines +101 to +103
Appwrite Cloud gives developers a fully managed backend so you can ship fast without provisioning or maintaining any infrastructure. You get storage, auth, databases, functions, and real-time out of the box, with file storage that scales automatically as your app grows. It provides server-side SDKs and SSR-friendly authentication, so you can fetch data and manage sessions securely on the server in frameworks like Next.js, Nuxt, and SvelteKit. With Databases, Storage, and Functions behind a clean API, the backend for your server-rendered app is ready to go.

Whether you're prototyping your next idea or scaling a production app, Appwrite gives you auth, databases, storage, functions, and real-time in one place, all open-source. [Sign up for Appwrite Cloud](https://cloud.appwrite.io/) or spin up a self-hosted instance in minutes, and give your next build a real backend to grow on.

@adityaoberai adityaoberai Jul 7, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should have more info on how Sites actually supports this, this is too generic

Comment on lines +96 to +98
Appwrite Cloud gives developers a fully managed backend so you can ship fast without provisioning or maintaining any infrastructure. You get storage, auth, databases, functions, and real-time out of the box, with file storage that scales automatically as your app grows. Its Databases product gives you full CRUD out of the box through a clean API and SDKs for every major platform, so you can create, read, update, and delete records without writing and maintaining your own endpoints. Built-in permissions and queries mean the hard parts are handled for you.

Whether you're prototyping your next idea or scaling a production app, Appwrite gives you auth, databases, storage, functions, and real-time in one place, all open-source. [Sign up for Appwrite Cloud](https://cloud.appwrite.io/) or spin up a self-hosted instance in minutes, and give your next build a real backend to grow on.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should have simple code examples here

Comment on lines +102 to +104
* [Appwrite Databases docs](https://appwrite.io/docs/products/databases)
* [Create and manage documents](https://appwrite.io/docs/products/databases/documents)
* [Appwrite quick start guides](https://appwrite.io/docs/quick-starts)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* [Appwrite Databases docs](https://appwrite.io/docs/products/databases)
* [Create and manage documents](https://appwrite.io/docs/products/databases/documents)
* [Appwrite quick start guides](https://appwrite.io/docs/quick-starts)
* [Appwrite Databases docs](/docs/products/databases)
* [Create and manage documents](/docs/products/databases/documents)
* [Appwrite quick start guides](/docs/quick-starts)


Appwrite Cloud gives developers a fully managed backend so you can ship fast without provisioning or maintaining any infrastructure. You get storage, auth, databases, functions, and real-time out of the box, with file storage that scales automatically as your app grows. It provides server-side SDKs and SSR-friendly authentication, so you can fetch data and manage sessions securely on the server in frameworks like Next.js, Nuxt, and SvelteKit. With Databases, Storage, and Functions behind a clean API, the backend for your server-rendered app is ready to go.

Whether you're prototyping your next idea or scaling a production app, Appwrite gives you auth, databases, storage, functions, and real-time in one place, all open-source. [Sign up for Appwrite Cloud](https://cloud.appwrite.io/) or spin up a self-hosted instance in minutes, and give your next build a real backend to grow on.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sites?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants