# Wasm Day KubeCon EU CFP 2023

Presentation: 25 minutes, 1 or 2 speaker{s) presenting on a topic
Intermediate: Mid-level experience
**Topic**: Wasm in the Cloud

## Title
WASI and the Cloud

## Abstract

:::success
Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include and what the presentation will cover. Do not be vague. Be sure your abstract complies with the Linux Foundation's Inclusive Language Initiative.

This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).

Remember that this description is what will make an attendee decide whether your session would be a good fit for them. Be sure to provide enough information to help attendees make the right choice. Be clear and concise. This description is also one of two primary factors the Program Committee will use to measure the strength and relevance of the presentation, making your abstract strong is essential.

The presentation selection process is very competitive, with many proposals rejected. A well-written, thoughtful, and enticing abstract will greatly increase the possibility ofing accepted.
:::

WASI Preview2 is the next major version of WASI, the WebAssembly System Interface. Dan will cover WASI's evolution from Preview1 to Preview2, design changes and coming features such as WASI sockets, with demos along the way illustrating how all of these technologies fit together.

This talk then will explain why WASI is not merely POSIX APIs, which leads into a discussion of WASI-Cloud, a family of interface proposals for common applications APIs, such as key-value stores, pub/sub, and SQL databases. It intends to make cloud-native and serverless application development simpler and more portable. It will show off some demos of Wasm microservices capable of doing service invocations, event streaming and state management.

Finally, this talk will conclude with a glimpse into the future of WASI. Attendees will leave with a comprehensive understanding of WASI and its place in the distributed application landscape.

## Benefits to the Ecosystem

:::success
This is your chance to elaborate, emphasize why your presentation has to be shown and why attendees should care. Tell us how the content of your presentation will help better the ecosystem or anything you wish to share with the co-chairs and program committee. We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation is just as important as the content and that second determining factor in acceptance.
:::

This talk will provide valuable insights for interested attendees to advance their understanding of WASI Preview2 and WASI-Cloud, two fast moving new technologies in the WASM ecosystem. The discussion will highlight new features and design changes for the next major version of WASI. Developers will learn how to create WASI services that use the socket APIs, a new and long-awaited addition to WASI, introduced in WASI Preview2.

We will also cover WASI-Cloud in detail. The audience will learn how to create cloud-native and serverless workloads by leveraging on WASI-Cloud's capabilities, like service-to-service invocation, connecting to databases, and calling cloud provider APIs.

We'll conclude the talk by exploring the future potential of WASI, ensuring attendees leave the talk aware of what to expect in the next 12 months of WASI development. The talk will provide a comprehensive understanding of WASI and Wasm's ability to integrate with external services, and its future potential.

## Outline

### What is WASI?

The WebAssembly System Interface, WASI is a standards forum for developing and eventually standardizing APIs for WebAssembly.

The initial focus is on non-Web use cases.

### WASI today: "Preview 1"

Preview 1 is out there!
- WASI "Preview 1" is an early release of WASI.
- It's supported in a wide range of source languages.
- It's implemented in numerous Wasm engines.
- It's used in production in several places.

Preview 1 has several limitations.
- It's limited to POSIX-like functionality and C-oriented APIs
- It lacks complete sockets.
- It doesn't have a clear story for virtualization or composition.

As we look ahead to where people want WASI to go, we know virtualization and composition will be critical.

POSIX was the obvious place to start, and gave us several advantages, but we need WASI to be more.

### WASI Preview 2

WASI Preview 2 is in development, and it's complete enough that you can try it out to day.

We have a Preview1-to-Preview2 adapter.

I'll show some small demos of it in action.

### Demos

`hello, the time is...` demo showing off hello world and the timezone API.

`sockets` demo that has a client and server talking to each other.

And it's not just for C! Bindings in Rust + Go + JS + more.

Sockets is an API a lot of people are looking forward to.

At the same time, when we look at Wasm's full potential, sockets are also very limiting.
They tie applications to traditional ways of doing networking.
Some of the most exciting opportunities with Wasm are the ways in which it can open up new kinds of applications.

### Intro to wasi-cloud

A single central world contains all of wasi-cloud SpiderLightning APIs.

Address why sockets are not enough. That it is coming.

### Demo

Similar to preview2-prototyping repo

Wasmtime CLI bundles all the wasi proposals.

`wasmtime cloud` feeds in a config.

Go beyond microservices: cut out the roundtrips.

### What's next? and When? Future is bright

Here is how it works today, but THIS is what we have planned for the future.

What's the effort needs to port legacy applications to wasi-cloud.

### Resources

...