Skip to content

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

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

SEO Blogs (CRUD, Database sharading, server-side rendering)#3087
aishwaripahwa12 wants to merge 3 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?", and "What is server-side rendering?" — each with cover images, FAQ frontmatter, and a resources section. All posts are marked unlisted: true, use valid author slugs, and have corresponding entries added to .optimize-cache.json.

  • Three new markdoc blog posts added under src/routes/blog/post/, each with structured frontmatter including FAQs, a cover image path, and an Appwrite "Start building" CTA.
  • Cover images committed as .avif files with .png cache entries in .optimize-cache.json, consistent with the project's existing image optimization pattern.
  • The sharding and SSR posts use absolute https://appwrite.io/docs/… URLs in their resources sections, while the CRUD post (and other existing "what-is-*" posts in the repo) use relative paths — these could be aligned for consistency.

Confidence Score: 5/5

Safe to merge — purely additive content changes with no logic, migrations, or breaking modifications.

All three posts are new markdown content files with no runtime logic. Author slugs and image cache entries are valid, and the posts are published as unlisted: true so there is no immediate public visibility risk.

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; well-structured frontmatter with valid author slug, FAQs, and resource links using relative paths.
src/routes/blog/post/what-is-database-sharding-a-beginners-guide/+page.markdoc New SEO blog post on database sharding; duplicate conclusion from a previous commit is resolved in the current state. Resource links use absolute URLs unlike the CRUD post.
src/routes/blog/post/what-is-server-side-rendering-a-beginners-guide/+page.markdoc New SEO blog post on server-side rendering; valid structure and content, resource links use absolute URLs.
.optimize-cache.json Three new cache entries added for the new blog cover images; all three new image files have corresponding cache entries (extension mismatch .avif vs .png is intentional per project convention).
static/images/blog/what-is-crud-explained/cover.avif New cover image for CRUD blog post.
static/images/blog/what-is-database-sharding-a-beginners-guide/cover.avif New cover image for database sharding blog post.
static/images/blog/what-is-server-side-rendering-a-beginners-guide/cover.avif New cover image for server-side rendering blog post.

Reviews (3): Last reviewed commit: "Apply suggestion from @adityaoberai" | 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 thread src/routes/blog/post/what-is-crud-explained/+page.markdoc Outdated

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?

Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
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