The short answer right now is no. The behavior of the default (and most popular) trigger in Spin (the HTTP trigger) is to create a new instance for handling each incoming request. We made that choice primarily because we want to leverage the really good startup times for Wasm (and in particular for Wasmtime), and not running any guest code (in this case, business logic) until there is an actual incoming request means the server can execute other applications while idle.

Now, HTTP workloads are not the only type of workloads that Spin can handle — because of the way it's built, it's entirely pluggable and you can build your own trigger (for example https://github.com/fermyon/spin-trigger-sqs), and potentially have long-running processes, but that is not currently possible with Spin today.

  Location: Mumbai, India(IST)
  Remote: Yes
  Willing to relocate: No
  Technologies: Backend Software Dev - JavaScript/TypeScript, Node.js, Postgres, 
                GCP, Docker/K8s, Nest.js
  Email: [email protected]

  ----

  I like doing backend stuffs, I primarily use Node.js for building Rest APIs 
  and scripts. Looking for remote position.

9+ years in senior/lead roles at startups and MNCs

I've mostly been working with Node.js the past several years. Significant experience with Javascript/ES6, PostgreSQL, Redis, HTML5, React, Docker, Kubernetes, GCP.

Open to part-time engagements.

Feel free to email: pradeepchauhan91 |@| gmail.com

Also I googled "adtech for dummies" it returned good results