wasmCloud / wasmCloud/wasmcloud.com

[FEAT] Concrete examples for high-level benefits

Open
#839 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
MDX
Stars
23
Forks
70
Avg merge
2d 1h
Merged PRs (30d)
17

Description

On our homepage we talk about the things we know and love about Wasm, wasmCloud, components, NATS, etc. I think we do a good job of tying some of those benefits to ideas in https://wasmcloud.com/docs/tour/why-wasmcloud/. What we are distinctly missing are concrete, to-the-point examples that show the difference between container-based applications and wasmCloud-based applications for our strengths.

Some of the things that we could have quick workflows/examples/docs pages around are:

  1. Demonstrating the scale-to-zero benefit
  2. Upgrading dependencies
  3. Component composition (perhaps wash work here to simplify tooling requirements)
  4. Running multiple components on different routes
  5. Cloud deployments
  6. The transition from dev -> production
  7. ...?
    Feedback generally adopted from https://news.ycombinator.com/item?id=43039962

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the homepage and the docs tour at docs/tour/why-wasmcloud/ to identify benefits that need concrete demonstrations. Review the proposed areas—scale-to-zero, dependency upgrades, component composition, routing, cloud deployment, and dev-to-production—and define a focused set of workflows. Done means the selected examples clearly compare container-based and wasmCloud-based applications.

Written by the indexing model from the issue text.

Assessment

Tech stack
wasm
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.