docs(seo): 6 more vs-competitor peer landings

[vieiralucas]

Batch 4B. Six more /vs/ peer landing pages.

• /vs/dynamodb-local/ — AWS's official DynamoDB emulator; fakecloud adds Streams-to-Lambda + 22 other services
• /vs/minio/ — MinIO is production S3-compatible storage; fakecloud is AWS-testing. Complementary, not competitive.
• /vs/s3mock/ — adobe/S3Mock is JVM S3-only
• /vs/aws-sdk-client-mock/ — in-process Node mocks; complementary test-pyramid tiers
• /vs/testcontainers/ — not a competitor; includes usage snippets in 5 languages
• /vs/elasticmq/ — Scala SQS-only

Honest positioning. 'Pick by fit' framing. No fabricated benchmarks. Each page documents when to pick the competitor, when fakecloud, when both.

---

Summary by cubic

Adds six SEO /vs competitor pages: /vs/dynamodb-local, /vs/minio, /vs/s3mock, /vs/aws-sdk-client-mock, /vs/testcontainers, and /vs/elasticmq. Each page explains when to choose the peer, when to use fakecloud, and when to use both, with clear guidance on cross-service flows, real Lambda triggers, and multi-language support.

^{Written for commit 8fb4a27. Summary will update on new commits.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[cubic-dev-ai]

3 issues found across 6 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="website/content/vs/elasticmq.md">

<violation number="1" location="website/content/vs/elasticmq.md:3">
P2: The service count is off here: fakecloud has 23 total services, so this should say 22 other AWS services.</violation>

<violation number="2" location="website/content/vs/elasticmq.md:29">
P2: ElasticMQ is not a full SQS API implementation; it only covers a subset of the SQS query interface.</violation>
</file>

<file name="website/content/vs/aws-sdk-client-mock.md">

<violation number="1" location="website/content/vs/aws-sdk-client-mock.md:52">
P3: The aws-sdk-client-mock side is not isolated per test by default; it requires an explicit `reset()`/`restore()` in test setup.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: ElasticMQ is not a full SQS API implementation; it only covers a subset of the SQS query interface.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At website/content/vs/elasticmq.md, line 29:

<comment>ElasticMQ is not a full SQS API implementation; it only covers a subset of the SQS query interface.</comment>

<file context>
@@ -0,0 +1,55 @@
+
+| | fakecloud | ElasticMQ |
+|---|---|---|
+| SQS operations | 23 | Full SQS API |
+| FIFO queues | Yes | Yes |
+| DLQ | Yes | Yes |
</file context>

[cubic-dev-ai]

P2: The service count is off here: fakecloud has 23 total services, so this should say 22 other AWS services.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At website/content/vs/elasticmq.md, line 3:

<comment>The service count is off here: fakecloud has 23 total services, so this should say 22 other AWS services.</comment>

<file context>
@@ -0,0 +1,55 @@
++++
+title = "fakecloud vs ElasticMQ"
+description = "How fakecloud compares to ElasticMQ. Both provide local SQS; fakecloud adds SNS fan-out, Lambda event source mappings, and 21 other AWS services."
+template = "page.html"
++++
</file context>

[cubic-dev-ai]

P3: The aws-sdk-client-mock side is not isolated per test by default; it requires an explicit reset()/restore() in test setup.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At website/content/vs/aws-sdk-client-mock.md, line 52:

<comment>The aws-sdk-client-mock side is not isolated per test by default; it requires an explicit `reset()`/`restore()` in test setup.</comment>

<file context>
@@ -0,0 +1,58 @@
+| Real cross-service wiring | Yes | No |
+| Works with Terraform/CDK | Yes | No |
+| Failure-path specificity | Medium (via normal AWS error codes) | High (script any response) |
+| Test isolation | `/_fakecloud/reset` or unique resource names | Per-test by default |
+
+## Links
</file context>