SEO Blogs by aishwaripahwa12 · Pull Request #2866 · appwrite/website

aishwaripahwa12 · 2026-04-07T06:41:56Z

2 SEO Blogs

greptile-apps · 2026-04-07T06:51:11Z

Greptile Summary

Adds two new SEO-oriented blog posts covering backend platform longevity and open-source maturity evaluation, each accompanied by a cover image and cache hash entry. Both posts are marked unlisted: true, have correct and distinct meta descriptions, valid author references (atharva and aditya-oberai), and all internal doc/product links resolve to existing paths.

Confidence Score: 5/5

Safe to merge — both posts are well-formed, correctly attributed, and all previously flagged issues have been resolved.

All prior P0/P1 concerns (mismatched description, broken internal links) from the previous review thread have been addressed. No new issues found. Remaining content is static markdown with no logic paths.

No files require special attention.

Vulnerabilities

No security concerns identified. The changes are static Markdoc content files and binary images with no code execution paths.

Important Files Changed

Filename	Overview
src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc	New SEO blog post on backend platform longevity; description matches content, author exists, all internal links are valid, marked unlisted.
src/routes/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc	New SEO blog post on evaluating OSS maturity; frontmatter is correct, author exists, all internal links point to valid paths, marked unlisted.
.optimize-cache.json	Adds two new cover image hash entries for the new blog posts; no issues.
static/images/blog/backend-platform-longevity-what-to-look-for-beyond-features/cover.png	New cover image for backend longevity post; binary file, no issues.
static/images/blog/how-to-evaluate-open-source-maturity-before-using-it-in-production/cover.png	New cover image for OSS maturity post; binary file, no issues.

_{Reviews (9): Last reviewed commit: "Apply suggestions from code review" | Re-trigger Greptile}

src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>

adityaoberai · 2026-04-07T19:59:29Z

src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc

+
+Most backend platform comparisons focus on features: which authentication methods are supported, how the database query API works, whether there's a serverless functions layer. These are the wrong questions to lead with.
+
+Features are table stakes. What actually determines whether a backend dependency was a good decision three years from now is whether the platform is still maintained, still trustworthy, and still something you can get off if you need to. Evaluating for longevity requires a different set of questions.


"table stakes" is not a term a lot of people will understand xD

adityaoberai · 2026-04-07T20:01:27Z

src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc

+
+# The real cost of a platform that doesn't last
+
+When a backend platform is deprecated, acquired and sunset, or abandoned by its maintainers, the teams built on it absorb the full migration cost. That cost is rarely just "update your imports." It means migrating data out of proprietary formats, rewriting authentication flows, rebuilding API integrations, and doing all of it while your production application continues to serve users.


We need slightly better context setting for that first sentence

Maybe even a little simplification

src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc

adityaoberai · 2026-04-07T20:08:53Z

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc

+
+# Assess the bus factor
+
+**Bus factor** refers to how many contributors would need to be hit by a bus before the project stalls. A project maintained by a single person is fundamentally higher risk than one with a team of active contributors, even if the solo maintainer is prolific.


I'd mention how this has been mentioned in the context of the software industry in the past

Then talk about the concerns of a low bus factor for any team and then correlate with OSS

Otherwise this can be a little too harsh xD

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc

adityaoberai · 2026-04-07T20:11:25Z

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc

+
+# How Appwrite scores against these criteria
+
+[Appwrite](https://github.com/appwrite/appwrite) is an open-source backend platform for web, mobile, and AI apps. It provides [authentication](/docs/products/auth), [databases](/docs/products/databases), [file storage](/docs/products/storage), [serverless functions](/docs/products/functions), real-time subscriptions, and messaging in a single deployable unit. It can be [self-hosted](/docs/advanced/self-hosting) on any Docker-compatible infrastructure or used via [Appwrite Cloud](https://cloud.appwrite.io).


No Sites mention?

This is a frequent issue and should be looked out for in advance

adityaoberai · 2026-04-07T20:11:41Z

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc

+# Evaluating Appwrite for your production stack
+
+Running through the evaluation framework above with Appwrite:


Incomplete ending

src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc

Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc

Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

new seo blogs

d98f0b2

greptile-apps bot reviewed Apr 7, 2026

View reviewed changes

aishwaripahwa12 and others added 4 commits April 7, 2026 12:35

Update +page.markdoc

d613a64

Apply suggestion from @greptile-apps[bot]

1c95b9a

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>

Update +page.markdoc

0f67163

Update +page.markdoc

bacc6e2

adityaoberai requested changes Apr 7, 2026

View reviewed changes

adityaoberai reviewed Apr 7, 2026

View reviewed changes

src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc Outdated Show resolved Hide resolved

adityaoberai and others added 4 commits April 8, 2026 01:42

Apply suggestion from @adityaoberai

5e33fd8

Apply suggestion from @adityaoberai

aa445b2

Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update +page.markdoc

1979310

Update +page.markdoc

7aea7fe

adityaoberai reviewed Apr 8, 2026

View reviewed changes

src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc Outdated Show resolved Hide resolved

Apply suggestion from @adityaoberai

52c6457

aishwaripahwa12 commented Apr 8, 2026

View reviewed changes

src/routes/blog/post/backend-platform-longevity-what-to-look-for-beyond-features/+page.markdoc Outdated Show resolved Hide resolved

Apply suggestion from @aishwaripahwa12

f5c350f

aishwaripahwa12 commented Apr 8, 2026

View reviewed changes

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc Outdated Show resolved Hide resolved

Apply suggestion from @aishwaripahwa12

3fd3621

adityaoberai reviewed Apr 8, 2026

View reviewed changes

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc Outdated Show resolved Hide resolved

adityaoberai reviewed Apr 8, 2026

View reviewed changes

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc Outdated Show resolved Hide resolved

adityaoberai reviewed Apr 8, 2026

View reviewed changes

...s/blog/post/how-to-evaluate-open-source-maturity-before-using-it-in-production/+page.markdoc Outdated Show resolved Hide resolved

adityaoberai approved these changes Apr 8, 2026

View reviewed changes

Apply suggestions from code review

972ba76

Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SEO Blogs#2866

SEO Blogs#2866
aishwaripahwa12 wants to merge 13 commits intomainfrom
aishwari/seoblogs3

aishwaripahwa12 commented Apr 7, 2026

Uh oh!

greptile-apps bot commented Apr 7, 2026 •

edited

Loading

Vulnerabilities

Uh oh!

Uh oh!

Uh oh!

Uh oh!

adityaoberai Apr 7, 2026

Uh oh!

adityaoberai Apr 7, 2026

Uh oh!

Uh oh!

adityaoberai Apr 7, 2026

Uh oh!

Uh oh!

adityaoberai Apr 7, 2026

Uh oh!

adityaoberai Apr 7, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants


		Most backend platform comparisons focus on features: which authentication methods are supported, how the database query API works, whether there's a serverless functions layer. These are the wrong questions to lead with.

		Features are table stakes. What actually determines whether a backend dependency was a good decision three years from now is whether the platform is still maintained, still trustworthy, and still something you can get off if you need to. Evaluating for longevity requires a different set of questions.


		# The real cost of a platform that doesn't last

		When a backend platform is deprecated, acquired and sunset, or abandoned by its maintainers, the teams built on it absorb the full migration cost. That cost is rarely just "update your imports." It means migrating data out of proprietary formats, rewriting authentication flows, rebuilding API integrations, and doing all of it while your production application continues to serve users.


		# Assess the bus factor

		Bus factor refers to how many contributors would need to be hit by a bus before the project stalls. A project maintained by a single person is fundamentally higher risk than one with a team of active contributors, even if the solo maintainer is prolific.


		# How Appwrite scores against these criteria

		[Appwrite](https://github.com/appwrite/appwrite) is an open-source backend platform for web, mobile, and AI apps. It provides [authentication](/docs/products/auth), [databases](/docs/products/databases), [file storage](/docs/products/storage), [serverless functions](/docs/products/functions), real-time subscriptions, and messaging in a single deployable unit. It can be [self-hosted](/docs/advanced/self-hosting) on any Docker-compatible infrastructure or used via [Appwrite Cloud](https://cloud.appwrite.io).

		# Evaluating Appwrite for your production stack

		Running through the evaluation framework above with Appwrite:

Conversation

aishwaripahwa12 commented Apr 7, 2026

Uh oh!

greptile-apps bot commented Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 5/5

Vulnerabilities

Important Files Changed

Uh oh!

Uh oh!

Uh oh!

Uh oh!

adityaoberai Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

adityaoberai Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

adityaoberai Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

adityaoberai Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

adityaoberai Apr 7, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

greptile-apps bot commented Apr 7, 2026 •

edited

Loading