A proposed WebAssembly System Interface API.

wasi-cloud-core is currently in Phase 1.

• Dan Chiarlone
• David Justice
• Jiaxiao Zhou
• Taylor Thomas

wasi-cloud-core should have at least two implementations (i.e., from service providers, and or cloud providers), and, at the very minimum, pass the testsuite for Windows, Linux, and MacOS.

• Introduction
• Out-of-Scope Capabilities (for now)

Note: This proposal currently only contains the proposed WIT interfaces; more work is necessary to fully document the proposal.

wasi-cloud-core World aims to provide a generic way for WASI applications to interact with services. This world is created by including many other WASI worlds being proposed in the WASI community. The following is a list of the worlds that are currently being included in wasi-cloud-core.

• wasi-keyvalue
• wasi-messaging
• wasi-http
• wasi-runtime-config
• wasi-blob-store

This list of services provide a set of capabilities that are common to many applications. Examples: handling an HTTP request, responding to a pub/sub message, storing a key/value pair, etc. It targets a wide range of applications, from long-running services to "bursty workloads" like Edge functions, serverless functions or Cloud events.

This set of capabilities are derived from the best practices of building distributed applications. It is not intended to be a complete set of capabilities, but rather are needed by 80% of applications.

• wasi-sql: the scope of the wasi:sql is not clear yet, and it is decided to be dropped from the wasi-cloud-core proposal.
• wasi-distributed-lock-service: the distributed lock service is a very specific service that is not needed by 80% of applications. It is decided to be dropped from the wasi-cloud-core proposal.