tpmccallum
commented
1 year ago - Explain synchronous vs concurrent; give examples of how traditional languages like Python etc, have ready-built libraries which make concurrency very easy to implement i.e.
import concurrent, setmax_workersin a thread pool executor and start calling etc. - Consider mentioning fan-out/fan-in pattern, monitoring, and potentially touching on connection timeouts etc.
- Mention WASI API for waiting for I/O events on multiple handles and potential first-class support for structured concurrency in WASI Component Model and WASI Preview 3.
- Suggest a temporary workaround and perhaps make an example up to demonstrate this in the docs
dicej
At present, whilst single outbound requests are supported; neither Spin nor Cloud supports being able to run multiple concurrent outgoing requests.
This could present a limitation to a user who is planning on building their application on Spin/Cloud. The following paragraph is a little more information Re: time/resources/practicability of having multiple concurrent outgoing requests supported.
One plan is to add first-class support for structured concurrency (which is needed for concurrent outgoing requests) to the WASI Component Model and WASI Preview 3. The timeline for such a task to be completed could take at least one year.
In the meantime, if concurrent outgoing requests are a high priority, then we could potentially emulate concurrent outgoing HTTP requests using WASI Preview 1 or 2 polling (a WASI API for waiting for I/O events on multiple handles).