[sehz]

There is a significant difference between doing stream processing at edges (client, producers) vs. inline. Similar to performing SQL query in client vs. done by the database server. Think of the WASM inline module as a stored procedure but for the stream (omitting other implementation details).

> How does it prevent that if a stream being processed contains > PII data?

At the execution time, the WASM module can't access any memory outside it is given. Fluvio's SPU control data flow from the stream to the WASM module. For the PII use case, data is only decrypted just before sent over to the WASM engine. And since the WASM module can't access any data or have access to any host-based resources, it can't leak anything.

The key architecture advantage of in-line processing is that we can move computation as close to storage as possible reducing cost and latency